Thread: diskspace bigger after a vacuum

diskspace bigger after a vacuum

From
Vincent van der Locht
Date:
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
entityto whom it is addressed. Axon Digital Design Group is neither liable for the proper nor for the complete
transmissionof the information contained in this communication nor for any delay in its receipt. Axon Digital Design
Groupdoes not guarantee that the integrity of this communication has been maintained nor that the communication is free
ofviruses, interceptions or interference. If you are not the intended recipient of this communication, you are hereby
notifiedthat reading, disseminating, distributing or copying this message is strictly prohibited. In that case please
returnthe communication to the sender and delete and destroy all copies. In carrying out its engagements, Axon Digital
DesignGroup applies general terms and conditions, which contain a clause that limits its liability. A copy of these
termsand conditions is available on request 
  free of charge.




Re: diskspace bigger after a vacuum

From
"Scott Marlowe"
Date:
On Wed, 2004-06-30 at 06:54, Vincent van der Locht wrote:
> 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.