Re: Review: Non-inheritable check constraints - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Review: Non-inheritable check constraints
Date
Msg-id CA+TgmoacgSA0h-sBexgfuVyPLsGH2Of6X+y+zN2k_tPV0kL3iA@mail.gmail.com
Whole thread Raw
In response to Re: Review: Non-inheritable check constraints  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: Review: Non-inheritable check constraints  (Nikhil Sontakke <nikkhils@gmail.com>)
List pgsql-hackers
On Fri, Dec 16, 2011 at 2:06 PM, Alvaro Herrera
<alvherre@commandprompt.com> wrote:
> Yeah.  Nikhil, Alex, this is the merged patch.  Have a look that it
> still works for you (particularly the pg_dump bits) and I'll commit it.
> I adjusted the regression test a bit too.

It seems hard to believe that ATExecDropConstraint() doesn't need any
adjustment.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: why do we need create tuplestore for each fetch?
Next
From: Robert Haas
Date:
Subject: Re: archive_keepalive_command