X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id A84CA9FB3D9 for ; Wed, 6 Sep 2006 16:43:39 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 33638-08-2 for ; Wed, 6 Sep 2006 19:43:35 +0000 (UTC) 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 C30B19FB3B6 for ; Wed, 6 Sep 2006 16:42:43 -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 k86Jgf9l023651; Wed, 6 Sep 2006 15:42:41 -0400 (EDT) To: Andrew Sullivan cc: pgsql-admin@postgresql.org Subject: Re: transactoin id wraparound problem In-reply-to: <20060906193208.GP362@phlogiston.dyndns.org> References: <6992E470F12A444BB787B5C937B9D4DF05ABC88F@ca-mail1.cis.local> <20060906193208.GP362@phlogiston.dyndns.org> Comments: In-reply-to Andrew Sullivan message dated "Wed, 06 Sep 2006 15:32:08 -0400" Date: Wed, 06 Sep 2006 15:42:41 -0400 Message-ID: <23650.1157571761@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200609/49 X-Sequence-Number: 22963 Andrew Sullivan writes: > On Wed, Sep 06, 2006 at 12:23:01PM -0700, Sriram Dandapani wrote: >> Is there a way to monitor vacuum progress. Can I resume normal >> operations assuming vacuum will update the transaction ids or should I >> wait till it finishes. > That depends on how many transactions you think will happen while > vacuum is running. If it's a lot, you could pass the fatal point (== > you lose data) before vacuum finishes. He's apparently running 8.1 (I don't think that error message wording exists in older releases), so what would happen is that the DB will refuse to start new transactions; but there won't be any data lost. Still it might be best to let the vacuum have all the machine's cycles to get done as fast as possible. regards, tom lane