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 12:26:44 -0400
Message-ID: <18569.1183652804@sss.pgh.pa.us> (raw)
In-Reply-To: <BA2CC7B7A60EF64B968B268B500397CB11B31E@migsexch01.miint.mistral.net>
References: <BA2CC7B7A60EF64B968B268B500397CB11B2FC@migsexch01.miint.mistral.net>
<11565.1183647202@sss.pgh.pa.us>
<BA2CC7B7A60EF64B968B268B500397CB11B31E@migsexch01.miint.mistral.net>
"James Wilford" <jwilford@mistral.net> writes:
> Its PG version 7.3.
Please tell us it's a relatively recent 7.3.x, at least ...
> I've just tried all your suggestions and
> unfortunately I still can't delete the bogus row. I think I managed to
> reindex the system tables:
Curious. I'd have thought the reindex would fail because of the
duplicate datname entries.
> And trying ctid didn't work, assuming this syntax is correct:
> backend> delete from pg_database where ctid = '(0,37)';
Even more curious. I'm starting to think it's some sort of XID
wraparound problem, except if you can see it in SELECT then why doesn't
the DELETE see it?
Could you show all the system columns of pg_database, viz
select xmin, cmin, xmax, cmax, oid, ctid, datname from pg_database;
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: <18569.1183652804@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