diskspace bigger after a vacuum

[Vincent van der Locht]

Hi,

I have a question, I wnat to use a postgresql database in a embedded
appliance, and thus want to keep the database as small as possible.
I'd noticed that de diskspace only grows when i do an VACUUM; or a
./vacuumdb. Can this be explained why this is? or why this can be?

i use postgresql 7.4.2 and run on fedora core 1.

greetz,
Vincent

The information contained in this communication is confidential and is intended solely for the use of the individual or entity to whom it is addressed. Axon Digital Design Group is neither liable for the proper nor for the complete transmission of the information contained in this communication nor for any delay in its receipt. Axon Digital Design Group does not guarantee that the integrity of this communication has been maintained nor that the communication is free of viruses, interceptions or interference. If you are not the intended recipient of this communication, you are hereby notified that reading, disseminating, distributing or copying this message is strictly prohibited. In that case please return the communication to the sender and delete and destroy all copies. In carrying out its engagements, Axon Digital Design Group applies general terms and conditions, which contain a clause that limits its liability. A copy of these terms and conditions is available on request
free of charge.




---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to ***@postgresql.org)

[Scott Marlowe]

Post by Vincent van der Locht
Hi,
I have a question, I wnat to use a postgresql database in a embedded
appliance, and thus want to keep the database as small as possible.
I'd noticed that de diskspace only grows when i do an VACUUM; or a
./vacuumdb. Can this be explained why this is? or why this can be?
i use postgresql 7.4.2 and run on fedora core 1.

I'd look at firebirdSQL for this kind of work. It has a naturally
smaller footprint, and can run, if I remember correctly, as a shared lib
right underneath your application.

Not that you can't slim down postgresql to fit on a smaller memory card
etc... but it's just not really built for this kind of application.


---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match