Skip site navigation (1) Skip section navigation (2)

Re: FW: More than 1 pg_database Entry for Database - Thread #2

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Samuel Stearns" <SStearns(at)internode(dot)com(dot)au>
Cc: <pgsql-admin(at)postgresql(dot)org>
Subject: Re: FW: More than 1 pg_database Entry for Database - Thread #2
Date: 2010-04-16 16:05:32
Message-ID: 4BC8447C02000025000309EA@gw.wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-admin
Samuel Stearns <SStearns(at)internode(dot)com(dot)au> 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

In response to

Responses

pgsql-admin by date

Next:From: Frederiko CostaDate: 2010-04-16 16:29:02
Subject: Re: archived WALL files question
Previous:From: Jose BerardoDate: 2010-04-16 15:15:13
Subject: Re: PostgreSQL with SSL

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group