pg_dump doesn't save altered column information for inherited columns

From: <depstein(at)alliedtesting(dot)com>
To: <pgsql-bugs(at)postgresql(dot)org>
Cc: <pgagarinov(at)alliedtesting(dot)com>
Subject: pg_dump doesn't save altered column information for inherited columns
Date: 2011-02-01 09:55:49
Message-ID: 29F36C7C98AB09499B1A209D48EAA615B501DA89D3@mail2a.alliedtesting.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hello,

I noticed that when pg_dump saves SQL code for a table with inheritance, it does not save any information about inherited columns. This is fine when inherited columns do not undergo any modification, but when they do, that information is lost.

Example:

create table parent (id integer not null);

create table child (value integer) inherits (parent);

alter table child alter column id drop not null;

insert into child values (null, 1);

Here is the code of the child table as generated by pg_dump:

CREATE TABLE child (
value integer
)
INHERITS (parent);

When the table is recreated using this code, the id column has the NOT NULL restriction, which was not present in the original.

I don't think this is right. Either inherited columns should be immune to changes, or else pg_dump should reflect those changes in its SQL code.

Dmitry

Dmitry Epstein | Developer
Allied Testing
T + 7 495 544 48 69 Ext 417
M + 7 926 215 73 36

www.alliedtesting.com<http://www.alliedtesting.com/>
We Deliver Quality.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Steve White 2011-02-01 11:21:20 Feature request: include script file into function body
Previous Message Tom Lane 2011-01-31 17:53:17 Re: BUG #5857: pg_restore --clean dropping type too soon