From: Tom Lane <tgl@sss.pgh.pa.us>
To: James Wilford <jwilford@mistral.net>
Cc: pgsql-admin@postgresql.org
Subject: Re: More than one pg_database entry for database
Date: Thu, 05 Jul 2007 13:38:49 -0400
Message-ID: <19238.1183657129@sss.pgh.pa.us> (raw)
In-Reply-To: <BA2CC7B7A60EF64B968B268B500397CB11B320@migsexch01.miint.mistral.net>
References: <BA2CC7B7A60EF64B968B268B500397CB11B2FC@migsexch01.miint.mistral.net>
<11565.1183647202@sss.pgh.pa.us>
<BA2CC7B7A60EF64B968B268B500397CB11B31E@migsexch01.miint.mistral.net>
<18569.1183652804@sss.pgh.pa.us>
<BA2CC7B7A60EF64B968B268B500397CB11B320@migsexch01.miint.mistral.net>
"James Wilford" <jwilford@mistral.net> writes:
> It's a redhat version of 7.3 - rh-postgresql-server-7.3.8-2 is the
> package.
That was obsoleted by Red Hat well over two years ago; you are overdue
for an update.
> xmin | cmin | xmax | cmax | oid | ctid | datname
> ----------+------------+------------+------+----------+--------+--------
> 59254726 | 0 | 0 | 0 | 31238435 | (0,28) | misp
> 2 | 2430588419 | 2430588419 | 0 | 6790290 | (0,37) | misp
It definitely looks to me like you have a problem with XID wraparound :-(
The (0,37) row was apparently deleted long ago, but never vacuumed away,
and now its xmax has wrapped around past the 2-billion-transaction event
horizon, causing it to appear visible to MVCC-using queries. So there's
something broken about your routine vacuuming procedures; you'd better
take a look at that.
As far as getting out of the situation, the only really good answer is a
dump and reload. I can't think of any simple way of getting rid of the
bogus row, but what you should be able to do to let pg_dump work is to
rename misp to something else. You can rename it back after getting
through the dump/reload, of course.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, jwilford@mistral.net
Subject: Re: More than one pg_database entry for database
In-Reply-To: <19238.1183657129@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox