From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org, Josh Berkus <josh(at)agliodbs(dot)com> |
Subject: | Re: Deferred partial/expression unique constraints |
Date: | 2011-07-13 15:26:37 |
Message-ID: | 4903.1310570797@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> writes:
>>> On 7/12/11 9:46 AM, Andres Freund wrote:
>>>> I guess $subject wasn't implemented because plain unique indexes aren't
>>>> represented in pg_constraint and thus do not have a place to store
>>>> information about being deferred?
> I agree that expressing that using a UNIQUE constraint would perhaps
> be more intuitive, but it would be new non-SQL-spec syntax that AFAICS
> wouldn't actually add any new functionality.
Our standard reason for not implementing UNIQUE constraints on
expressions has been that then you would have a thing that claims to be
a UNIQUE constraint but isn't representable in the information_schema
views that are supposed to show UNIQUE constraints. We avoid this
objection in the current design by shoving all that functionality into
EXCLUDE constraints, which are clearly outside the scope of the spec.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2011-07-13 15:41:50 | Re: Need help understanding pg_locks |
Previous Message | Tom Lane | 2011-07-13 14:59:36 | Re: Tweaking the planner's heuristics for small/empty tables |