Re: how to create a non-inherited CHECK constraint in CREATE TABLE - Mailing list pgsql-hackers

From Nikhil Sontakke
Subject Re: how to create a non-inherited CHECK constraint in CREATE TABLE
Date
Msg-id CANgU5Zff1a-e2_VAjdcOKypiweTq-Gm+RacUTRkEB5PaeE9jBg@mail.gmail.com
Whole thread Raw
In response to Re: how to create a non-inherited CHECK constraint in CREATE TABLE  (Jim Nasby <jim@nasby.net>)
Responses Re: how to create a non-inherited CHECK constraint in CREATE TABLE  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
 
>> It appears that the only way to create a non-inherited CHECK constraint
>> is using ALTER TABLE.  Is there no support in CREATE TABLE planned?
>> That looks a bit odd.
>
> There are no plans to do that AFAIR, though maybe you could convince
> Nikhil to write the patch to do so.

That certainly doesn't meet the principle of least surprise... CREATE TABLE should support this.

Well, the above was thought about during the original discussion and eventually we felt that CREATE TABLE already has other issues as well, so not having this done as part of creating a table was considered acceptable then:

http://postgresql.1045698.n5.nabble.com/Check-constraints-on-partition-parents-only-tt4633334.html#a4647144

But, let me have a stab at it when I get some free cycles. 

Regards,
Nikhils

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [v9.2] LEAKPROOF attribute of FUNCTION (Re: [v9.2] Fix Leaky View Problem)
Next
From: Noah Misch
Date:
Subject: Re: psql \timing vs failed statements