pg_dump does not reflect changes in column names with primary keys - Mailing list pgsql-bugs

From pgsql-bugs@postgresql.org
Subject pg_dump does not reflect changes in column names with primary keys
Date
Msg-id 200009050715.e857Fn911972@hub.org
Whole thread Raw
List pgsql-bugs
Edward Pilipczuk (edx@pagi.pl) reports a bug with a severity of 3
The lower the number the more severe it is.

Short Description
pg_dump does not reflect changes in column names with primary keys

Long Description
If a table with primary key is created (CREATE TABLE), that implicitly forces also creating an index table, and after
creationthe name of that column is renamed (ALTER TABLE), the we get problem with indexing. The index table still
behavesin "old fashion", i.e.,  
it reflects the original primary key. It influences also pg_dump bahaviour. The error is reported when restoring data
basedumped  
previously by pg_dump utility. The workaround I've found here is to edit manually dump file in order to correct the
nameof the index table. Then restoring works fine. 


Sample Code


No file was uploaded with this report

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: psql can crash the backend on login
Next
From: pgsql-bugs@postgresql.org
Date:
Subject: Access 97 and PSQL ODBC