BUG #3973: pg_dump using inherited tables do not always restore - Mailing list pgsql-bugs

From Alex Hunsaker
Subject BUG #3973: pg_dump using inherited tables do not always restore
Date
Msg-id 200802202103.m1KL3Tux029173@wwwmaster.postgresql.org
Whole thread Raw
Responses Re: BUG #3973: pg_dump using inherited tables do not always restore  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
The following bug has been logged online:

Bug reference:      3973
Logged by:          Alex Hunsaker
Email address:      badalex@gmail.com
PostgreSQL version: 8.3.0
Operating system:   Linux
Description:        pg_dump using inherited tables do not always restore
Details:

create table junk (val integer not null, val2 integer);
create table junk_child () inherits (junk_1);
alter table junk_child alter column val drop not null;
insert into junk_child (val2) values (1);

pg_dump -t junk -t junk_child

pg_restore/psql will fail because junk_child.val now has a not null
constraint

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #3969: pg_ctl cannot detect server startup
Next
From: Tom Lane
Date:
Subject: Re: BUG #3973: pg_dump using inherited tables do not always restore