From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thomas F. O'Connell <tfo@sitening.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: vacuumdb vs. max_connections: SELECT waiting
Date: Fri, 12 May 2006 23:08:17 -0400
Message-ID: <25842.1147489697@sss.pgh.pa.us> (raw)
In-Reply-To: <BC924EDD-8D0E-4A3D-AE9A-B43AF7770BC1@sitening.com>
References: <BC924EDD-8D0E-4A3D-AE9A-B43AF7770BC1@sitening.com>
"Thomas F. O'Connell" <tfo@sitening.com> writes:
> Shortly after I kicked it off, I watched the number of connections
> trend upward as a result of the aggressive locking of FULL. I didn't
> want to let this continue without notifying the developers about a
> potential downtime for their application, so I killed the vacuumdb
> process I had started, figuring that the existing connections would
> go right through.
Killing the vacuumdb client process wouldn't automatically abort the
current operation of the connected backend. If that's all you did,
it would've finished out the VACUUM command, ie, essentially no effect.
Sending a SIGINT to the backend to cancel the current command would've
been the right thing to do.
> Can autovacuum recover for the months where
> the FSM settings were not sufficient to cover the number of relations
> in this cluster?
Probably not. But VACUUM FULL isn't really a great choice either;
it will certainly do nothing at all for index bloat. You might try
CLUSTER instead if you need to aggressively recover space.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, tfo@sitening.com
Subject: Re: vacuumdb vs. max_connections: SELECT waiting
In-Reply-To: <25842.1147489697@sss.pgh.pa.us>
References: <BC924EDD-8D0E-4A3D-AE9A-B43AF7770BC1@sitening.com> <25842.1147489697@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox