Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 3ACBC475EF7 for ; Wed, 20 Nov 2002 14:32:38 -0500 (EST) Received: from mail1.ihs.com (mail1.ihs.com [170.207.70.222]) by postgresql.org (Postfix) with ESMTP id 7E6B2475B8E for ; Wed, 20 Nov 2002 14:32:37 -0500 (EST) Received: from css120.ihs.com (css120.ihs.com [170.207.105.120]) by mail1.ihs.com (8.12.6/8.12.6) with ESMTP id gAKJVuGx023077; Wed, 20 Nov 2002 12:31:56 -0700 (MST) Date: Wed, 20 Nov 2002 12:32:40 -0700 (MST) From: "scott.marlowe" To: Francisco Reyes Cc: Medi Montaseri , pgsql General List Subject: Re: Closing inactive connections OR user connections limits In-Reply-To: <20021120135345.S30106-100000@zoraida.natserv.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-MailBodyFilter: Message body has not been filtered X-MailScanner: Found to be clean X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200211/866 X-Sequence-Number: 33287 On Wed, 20 Nov 2002, Francisco Reyes wrote: > On Wed, 20 Nov 2002, Medi Montaseri wrote: > > > In 7.2, you can run the vacuum in parallel with other database activities... > > As far as I know this is not the case for "vacuum full". The thing that blocks vacuum full are pending transactions. If the connections aren't holding open a transaction the vacuum full will run just fine. For most folks, daily / hourly vacuums (not full vacuums) in 7.2 are all you need, with a weekly or so vacuum full.