> 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?
So I guess I should also ask if there's anything I could do to give you more information about how this might have happened? Would it be helpful to brute-force rename the bogus entry and submit a dump of the schema? -- Scott Ribe [EMAIL PROTECTED] http://www.killerbytes.com/ (303) 665-7007 voice ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
