Re: BUG #5259: the table name double - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #5259: the table name double
Date
Msg-id 15920.1262627724@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #5259: the table name double  (Craig Ringer <craig@postnewspapers.com.au>)
List pgsql-bugs
Craig Ringer <craig@postnewspapers.com.au> writes:
> On 4/01/2010 2:26 PM, David wrote:
>> the table name double,why?

> How about some information?

A reasonable bet is that the pg_namespace row for "public" has gotten
duplicated (either in reality, or there's an extra index entry for it).
Which would cause the join in psql's \dp query to show tables in that
schema twice.  So what I'd like to see is the output of
    select ctid,xmin,xmax,nspname from pg_namespace;

Also the exact backend version, as you previously mentioned.

A quick look through the 8.0.x CVS history shows at least one
long-since-fixed bug that could have resulted in duplicate rows or
duplicate index entries.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Robert Haas
Date:
Subject: Re: BUG #5260: Postgre crashed unexpectedly
Next
From: Robert Haas
Date:
Subject: Re: BUG #5258: Unique and foreign key constraints fail on columns with reserved names, but not check constraints