Re: BUG #8247: Duplicate database names - pg_dump backup fails - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #8247: Duplicate database names - pg_dump backup fails
Date
Msg-id 21467.1371837805@sss.pgh.pa.us
Whole thread Raw
In response to BUG #8247: Duplicate database names - pg_dump backup fails  (paul.macdonald@ssc-spc.gc.ca)
List pgsql-bugs
paul.macdonald@ssc-spc.gc.ca writes:
> Postgres version: 7.4.7-6sarge1

Egad.  Not only has 7.4 been EOL for years, but the last release in that
series was 7.4.30.  You are missing many years' worth of bug fixes.
You really, really, really need to get off of that PG version ASAP.

> Issue: pg_dump fails due to unexpected duplication of database name
> ("avipads"). Dropdb will remove one instance of the database name, but
> unable to remove the second instance.

I suspect this is evidence of transaction ID wraparound in the
pg_database catalog.  See if "VACUUM FULL pg_database" makes things
any saner.  (Delete the one database that you're able to get rid of
first.)

            regards, tom lane

pgsql-bugs by date:

Previous
From: paul.macdonald@ssc-spc.gc.ca
Date:
Subject: BUG #8247: Duplicate database names - pg_dump backup fails
Next
From: Tom Lane
Date:
Subject: Re: BUG #8245: Urgent:Query on slave failing with invalid memory alloc request size 18446744073709537559