| From: | Nikhil Sontakke <nikhil(dot)sontakke(at)enterprisedb(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Nikhil Sontakke <nikkhils(at)gmail(dot)com>, Alex Hunsaker <badalex(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Jerry Sievers <gsievers19(at)comcast(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Check constraints on partition parents only? |
| Date: | 2011-07-29 13:47:52 |
| Message-ID: | CABamaqNPg-r2Gi9n-NsptwyDu17TE4iOhcHWHPSE1cCksMN6EQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > Yeah, I have already hacked it a bit. This constraint now needs to be
> > spit out later as an ALTER command with ONLY attached to it
> > appropriately. Earlier all CHECK constraints were generally emitted as
> > part of the table definition itself.
>
> Hrm. That doesn't seem so good. Maybe we've got the design wrong
> here. It doesn't seem like we want to lose the ability to define
> arbitrary constraints at table-creation time.
>
>
Well the handling is different now for "ONLY" constraints only. The normal
constraints can still be attached at table-creation time.
Regards,
Nikhils
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nikhil Sontakke | 2011-07-29 13:49:52 | Re: Check constraints on partition parents only? |
| Previous Message | Tom Lane | 2011-07-29 13:45:39 | Re: Check constraints on partition parents only? |