BUG #3234: pg_dump uses the first version of a primary key's name when generating reports - Mailing list pgsql-bugs

From Jonathan Vanasco
Subject BUG #3234: pg_dump uses the first version of a primary key's name when generating reports
Date
Msg-id 200704171847.l3HIlBTj042755@wwwmaster.postgresql.org
Whole thread Raw
List pgsql-bugs
The following bug has been logged online:

Bug reference:      3234
Logged by:          Jonathan Vanasco
Email address:      postgres@2xlp.com
PostgreSQL version: 8.2.3
Operating system:   freebsd 6.1 , osx 10.4.9
Description:        pg_dump uses the first version of a primary key's name
when generating reports
Details:

reposted from pg-users, sorry for posting in the wrong place:

i believe i found a bug

    psql> create table test_failure ( id integer primary key );
    psql> alter table test_failure alter id rename to id_new ; # not relevant,
just illustrating the reason how i got to step 2
    psql> alter table test_failure_pkey rename to test_failure_id_new_pkey;

    $ pg_dump --schema-only -ttest_failure -Utest > test.sql

the pkey in the schema is added as 'test_failure_pkey' , not
'test_failure_id_new_pkey';

it happens whether or not you use 'alter table' or 'alter index' on the pkey
name

pgsql-bugs by date:

Previous
From: "Christian Gonzalez"
Date:
Subject: BUG #3236: Partitioning has problem with timestamp and timestamptz data type
Next
From: "Dmitry Belyavsky"
Date:
Subject: BUG #3233: Trigger checks failed on concurrent transactions