Re: Can't pg_dumpall, claims database exists twice

Scott Ribe <scott_ribe@killerbytes.com> writes:
>> Now how the heck did that happen?  That's not some kind of weird UPDATE
>> failure, because the rows have different OIDs ... it seems like the
>> newer row must have been explicitly inserted, and it should surely have
>> been blocked by the unique index on datname.  Are there subdirectories
>> under $PGDATA/base for both of those OIDs?

> No, in fact there is only template1, template0, and 1 of the pedcard
> instances. Am I right that this simplifies things greatly?

Yeah, you can just brute-force delete the row with the OID that doesn't
correspond to any existing subdirectory.  But that makes it even odder
... where did that row come from???  Have you done any database-level
operations at all lately?

            regards, tom lane