Autovacuum is generally more effective as it can run when it needs to not having to wait til the end of the day. If you delete big chunks several times a day autovac can keep up. Also, it's enabled by default in 8.4 and up so the end user would have to actively turn it off in this instance. On Fri, Mar 18, 2011 at 6:21 AM, Voils, Steven M <steve@xxxxxxxxxxxxxxxx> wrote: > Our application supports pg 8.4 onwards. The vacuums are run automatically by the application rather than requiring end users to enable autovacuum; the vacuums being performed are regular. > > -----Original Message----- > From: Scott Marlowe [mailto:scott.marlowe@xxxxxxxxx] > Sent: Thursday, March 17, 2011 6:31 PM > To: Voils, Steven M > Cc: pgsql-general@xxxxxxxxxxxxxx > Subject: Re: Primary key vs unique index > > On Thu, Mar 17, 2011 at 12:59 PM, Voils, Steven M > <steve@xxxxxxxxxxxxxxxx> wrote: >> Thanks for the reply. I should have mentioned in the first post that we do delete significant amounts of the table which I thought was the cause of the bloat. We are already performing automatic vacuums nightly. > > Automatic regular vacuums? So you do or don't have autovac turned on? > > What version of pg are you running (8.3 or before, 8.4 or later?) > > Are your nightly vacuums FULL or regular vacuums? > -- To understand recursion, one must first understand recursion. -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
