X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 523629FA15C for ; Sat, 13 May 2006 00:08:24 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 77806-02 for ; Sat, 13 May 2006 00:08:20 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id B86CC9FA294 for ; Sat, 13 May 2006 00:08:18 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k4D38Hnh025843; Fri, 12 May 2006 23:08:17 -0400 (EDT) To: "Thomas F. O'Connell" cc: pgsql-admin@postgresql.org Subject: Re: vacuumdb vs. max_connections: SELECT waiting In-reply-to: References: Comments: In-reply-to "Thomas F. O'Connell" message dated "Fri, 12 May 2006 20:13:14 -0500" Date: Fri, 12 May 2006 23:08:17 -0400 Message-ID: <25842.1147489697@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/164 X-Sequence-Number: 21696 "Thomas F. O'Connell" 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