From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Fetter <david(at)fetter(dot)org>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: CREATE FOREGIN TABLE LACUNA |
Date: | 2012-03-14 22:20:02 |
Message-ID: | CA+Tgmoarvpcr6Nu10mrE6f4beh4NYGdxmHDHTtgs8zSC=OWV7A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Mar 14, 2012 at 5:21 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> On ons, 2012-03-14 at 17:16 -0400, Robert Haas wrote:
>> If a constraint is NOT ENFORCED, then the query planner presumably
>> won't rely on it for planning purposes
>
> Why do you presume that?
Well, as Tom alludes to, I'm guessing that NOT ENFORCED is not a
license to deliver wrong answers. But also as Tom says, what does the
spec say?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Farina | 2012-03-14 22:20:42 | Re: Faster compression, again |
Previous Message | Noah Misch | 2012-03-14 22:10:00 | Re: foreign key locks, 2nd attempt |