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 9886F9FB3A6 for ; Wed, 6 Sep 2006 19:05:03 -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 74622-05 for ; Wed, 6 Sep 2006 22:04:51 +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 A28809FB3A5 for ; Wed, 6 Sep 2006 19:04:51 -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 k86M4juU025553; Wed, 6 Sep 2006 18:04:45 -0400 (EDT) To: Scott Marlowe cc: Sriram Dandapani , pgsql-admin@postgresql.org Subject: Re: transactoin id wraparound problem In-reply-to: <1157577495.20424.29.camel@state.g2switchworks.com> References: <6992E470F12A444BB787B5C937B9D4DF05ABC8C7@ca-mail1.cis.local> <1157577495.20424.29.camel@state.g2switchworks.com> Comments: In-reply-to Scott Marlowe message dated "Wed, 06 Sep 2006 16:18:16 -0500" Date: Wed, 06 Sep 2006 18:04:45 -0400 Message-ID: <25552.1157580285@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200609/57 X-Sequence-Number: 22971 Scott Marlowe writes: > The most common cause of these problems is that you have long standing > transactions that never get closed. That can cause table bloat but it shouldn't have anything to do with XID wraparound problems. My guess is that the vacuum attempts are failing somewhere along the line, and that some perusal of the postmaster log would shed light on the issue. regards, tom lane