From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: 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 14:17:16 -0400
Message-ID: <19714.1183659436@sss.pgh.pa.us> (raw)
In-Reply-To: <20070705175304.GL5500@alvh.no-ip.org>
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>
<19238.1183657129@sss.pgh.pa.us>
<20070705175304.GL5500@alvh.no-ip.org>
Alvaro Herrera <alvherre@commandprompt.com> writes:
> Tom Lane wrote:
>> 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.
> Or roll the XID counter back, vacuum the table, and restore the XID to
> the original value. This is done with pg_resetxlog, though I am not
> sure if we shipped it in 7.3.
That seems fairly hazardous, in particular there might be undesirable
side-effects on other system catalogs while you are running with the
set-back XID counter.
Also, I see no very good reason to assume that this is the only
wraparound problem present in the DB. A dump and reload would probably
be useful to help check for other inconsistencies.
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, alvherre@commandprompt.com, jwilford@mistral.net
Subject: Re: More than one pg_database entry for database
In-Reply-To: <19714.1183659436@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