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

pg_dump does not reflect changes in column names with primary keys

From: pgsql-bugs(at)postgresql(dot)org
To: pgsql-bugs(at)postgresql(dot)org
Subject: pg_dump does not reflect changes in column names with primary keys
Date: 2000-09-05 07:15:49
Message-ID: 200009050715.e857Fn911972@hub.org (view raw or flat)
Thread:
Lists: pgsql-bugs
Edward Pilipczuk (edx(at)pagi(dot)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 creation the name of that column is renamed (ALTER TABLE), the we get problem with indexing. The index table still behaves in "old fashion", i.e., 
it reflects the original primary key. It influences also pg_dump bahaviour. The error is reported when restoring data base dumped 
previously by pg_dump utility. The workaround I've found here is to edit manually dump file in order to correct the name of the index table. Then restoring works fine.


Sample Code


No file was uploaded with this report


pgsql-bugs by date

Next:From: pgsql-bugsDate: 2000-09-05 13:33:21
Subject: Access 97 and PSQL ODBC
Previous:From: Tom LaneDate: 2000-09-03 22:16:33
Subject: Re: psql can crash the backend on login

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