BUG #3973: pg_dump using inherited tables do not always restore

From: "Alex Hunsaker" <badalex(at)gmail(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #3973: pg_dump using inherited tables do not always restore
Date: 2008-02-20 21:03:29
Message-ID: 200802202103.m1KL3Tux029173@wwwmaster.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-patches


The following bug has been logged online:

Bug reference: 3973
Logged by: Alex Hunsaker
Email address: badalex(at)gmail(dot)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

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2008-02-20 22:55:06 Re: BUG #3973: pg_dump using inherited tables do not always restore
Previous Message Tom Lane 2008-02-20 18:14:52 Re: BUG #3969: pg_ctl cannot detect server startup

Browse pgsql-patches by date

  From Date Subject
Next Message Jan Wieck 2008-02-20 21:14:58 Re: Proposed patch to change TOAST compression strategy
Previous Message Tom Lane 2008-02-20 18:14:52 Re: BUG #3969: pg_ctl cannot detect server startup