Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 6078C632369 for ; Fri, 16 Apr 2010 13:05:51 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 96045-05 for ; Fri, 16 Apr 2010 16:05:40 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from gw.wicourts.gov (gwmta.wicourts.gov [165.219.244.99]) by mail.postgresql.org (Postfix) with ESMTP id B0B496342CE for ; Fri, 16 Apr 2010 13:05:38 -0300 (ADT) Received: from Courts-MTA by gw.wicourts.gov with Novell_GroupWise; Fri, 16 Apr 2010 11:05:37 -0500 Message-Id: <4BC8447C02000025000309EA@gw.wicourts.gov> X-Mailer: Novell GroupWise Internet Agent 8.0.1 Date: Fri, 16 Apr 2010 11:05:32 -0500 From: "Kevin Grittner" To: "Samuel Stearns" Cc: Subject: Re: FW: More than 1 pg_database Entry for Database - Thread #2 References: <68B59BEDCD36854AADBDF17E91B2937AB89DE7F7@EXCHMAIL.staff.internode.com.au> In-Reply-To: <68B59BEDCD36854AADBDF17E91B2937AB89DE7F7@EXCHMAIL.staff.internode.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201004/216 X-Sequence-Number: 34310 Samuel Stearns wrote: > I am running version 8.3.3 and encountered a problem > Does anyone have any ideas how I can keep from getting into this > duplicate database scenario? Any advice would be greatly > appreciated. > it was stated by Tom Lane that the large xmax number may indicate > a problem with xid wraparound and that the problem row was never > vacuumed away due to broken vacuuming procedures. Applying the last 22 months of bug fixes would be a good start. http://www.postgresql.org/support/versioning http://www.postgresql.org/docs/8.3/static/release.html http://www.postgresql.org/download/ Autovacuum is supposed to protect you from wraparound, so it appears to have fallen down somehow. There were fixes for autovacuum bugs in 8.3.4 and 8.3.6, so it's entirely possible that just moving to 8.3.somethingrecent will prevent a recurrence. -Kevin