Re: ALTER TABLE...ALTER COLUMN vs inheritance

From: Bernd Helmle <mailings(at)oopsware(dot)de>
To: Bernd Helmle <mailings(at)oopsware(dot)de>, Selena Deckelmann <selenamarie(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ALTER TABLE...ALTER COLUMN vs inheritance
Date: 2010-09-14 22:41:19
Message-ID: CA2E4C4762EAE28D68404E75@amenophis
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

--On 23. Juli 2010 09:23:56 +0200 Bernd Helmle <mailings(at)oopsware(dot)de> wrote:

> I'm going to delay this patch until the next commitfest. I'm able to work
> on it only sporadically during the next two weeks, and some remaining
> issues need my attention on this patch:
>
> - ALTER TABLE SET NOT NULL works not properly
> - ALTER TABLE child NO INHERIT parent leaves inconistent state in
> pg_constraint
> - Special case in pg_get_constraintdef_worker() needs more thinking

Attached is my current progress on this work. It handles ALTER TABLE ...
[NO] INHERIT and NOT NULL constraints the same way we do with CHECK
constraints now. ALTER TABLE SET NOT NULL still lags support for this (ran
out of time to this commitfest deadline), but if nobody complains i would
like to add this to the current commitfest as WIP to hear other opinions
about the current approach again.

--
Thanks

Bernd

Attachment Content-Type Size
notnull_constraint.patch application/octet-stream 46.1 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-09-14 22:49:29 Re: top-level DML under CTEs
Previous Message Kevin Grittner 2010-09-14 21:49:48 Re: Serializable Snapshot Isolation