Craig Ringer <craig(at)postnewspapers(dot)com(dot)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
In response to
pgsql-bugs by date
|Next:||From: Ben Woosley||Date: 2010-01-04 17:57:42|
|Subject: Re: BUG #5258: Unique and foreign key constraints fail on columns with reserved names, but not check constraints|
|Previous:||From: Robert Haas||Date: 2010-01-04 17:24:02|
|Subject: Re: BUG #5260: Postgre crashed unexpectedly|