Skip site navigation (1) Skip section navigation (2)

Re: BUG #5259: the table name double

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
Cc: David <goodomens(at)21cn(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5259: the table name double
Date: 2010-01-04 17:55:24
Message-ID: 15920.1262627724@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
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 WoosleyDate: 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 HaasDate: 2010-01-04 17:24:02
Subject: Re: BUG #5260: Postgre crashed unexpectedly

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group