> It seems much more restrictive than necessary, plus it does nothing
> for the check-constraint case. My recollection of the previous
> discussion about how to fix this was that we needed to add an inhcount
> column to pg_constraint, and add entries for not-null constraints (at
> least inh
"Alex Hunsaker" <[EMAIL PROTECTED]> writes:
> On Wed, Feb 20, 2008 at 3:55 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
>> Actually the bug is that ALTER TABLE allows you to do that. It should
>> not be possible to drop an inherited constraint, but right now there's
>> not enough information in the sys
On Wed, Feb 20, 2008 at 3:55 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Alex Hunsaker" <[EMAIL PROTECTED]> writes:
> > 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
"Alex Hunsaker" <[EMAIL PROTECTED]> writes:
> 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/p
The following bug has been logged online:
Bug reference: 3973
Logged by: Alex Hunsaker
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.0
Operating system: Linux
Description:pg_dump using inherited tables do not always restore
Details:
create table junk (val
