Your table size should stabilize to the size you currently get before VACUUM FULL.... If you're afraid about having too many "deleted" rows, you just have to run VACUUM more often... I think that you have to test how often you have to run VACUUM so that your performance is not impacted.... Or perhaps you could try pg_autovacuum which will run VACUUM for you based on statistics... Regards, Patrick ---------------------------------------------------------------------------- --------------- Patrick Fiche email : patrick.fiche@xxxxxxxxxxx tel : 01 69 29 36 18 ---------------------------------------------------------------------------- --------------- -----Original Message----- From: pgsql-general-owner@xxxxxxxxxxxxxx [mailto:pgsql-general-owner@xxxxxxxxxxxxxx]On Behalf Of Bohdan Linda Sent: mercredi 31 aout 2005 14:19 To: Ben-Nes Yonatan Cc: pgsql-general@xxxxxxxxxxxxxx Subject: Re: detection of VACUUM in progress > > From the postgresql manual > http://www.postgresql.org/docs/8.0/interactive/maintenance.html : > " The standard form of VACUUM is best used with the goal of maintaining > a fairly level steady-state usage of disk space. If you need to return > disk space to the operating system you can use VACUUM FULL ? but what's > the point of releasing disk space that will only have to be allocated > again soon? Moderately frequent standard VACUUM runs are a better > approach than infrequent VACUUM FULL runs for maintaining > heavily-updated tables." > > From this I conclude that an ordinary VACUUM is sufficent to your > purpose cause you insert/delete almost the same amount of data daily. > > But then again I can be mistaken so if anyone can back me up here or > throw the manual on me will be nice ;P If I vacuum only the table, the records may be used by new lines, that is fine. Problem is, that when creating select on such table, it takes more pages to be read from the IO (it will read laso deleted rows) thus the select will last a bit longer. regards, Bohdan ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org
