| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Nikhil Sontakke <nikkhils(at)gmail(dot)com> |
| Cc: | 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:34:43 |
| Message-ID: | CA+Tgmob9H6iFwwNdnSBXyJyn51uZ0hpwW6ZR=2cKBv+Z6Q-LDg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jul 29, 2011 at 8:30 AM, Nikhil Sontakke <nikkhils(at)gmail(dot)com> wrote:
> 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.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-07-29 13:37:01 | Re: Check constraints on partition parents only? |
| Previous Message | Nikhil Sontakke | 2011-07-29 12:30:27 | Re: Check constraints on partition parents only? |