Re: BUG #5259: the table name double

From: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
To: David <goodomens(at)21cn(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5259: the table name double
Date: 2010-01-04 07:50:02
Message-ID: 4B419DAA.8070403@postnewspapers.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 4/01/2010 2:26 PM, David wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5259
> Logged by: David
> Email address: goodomens(at)21cn(dot)com
> PostgreSQL version: 8.0
> Operating system: RHEL5
> Description: the table name double
> Details:
>
> hi
>
> the table name double,why?

How about some information?

Is this the output of psql's `\dp' command? If so, where are the actual
privelege rows - did you delete them, or is the output you pasted
actually EXACTLY what came out of psql?

What version of the ancient and approaching-retirement 8.0 are you
using? "select pg_version()".

What's the output of this query:

\o output.txt
SELECT c.oid AS coid, n.oid AS noid, c.relname AS "Name", n.nspname
AS "namespace" FROM pg_catalog.pg_class c LEFT OUTER JOIN
pg_catalog.pg_namespace n ON n.oid = c.relnamespace WHERE c.relkind IN
('r', 'v', 'S');
\o

Please attach "output.txt" rather than copying and pasting, so that line
wrapping is preserved.

--
Craig Ringer

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Jasen Betts 2010-01-04 10:06:48 Re: BUG #5258: Unique and foreign key constraints fail on columns with reserved names, but not check constraints
Previous Message David 2010-01-04 06:26:18 BUG #5259: the table name double