| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: EXLCUDE constraints and Hash indexes |
| Date: | 2016-08-19 23:39:04 |
| Message-ID: | fb020e05-02c1-445f-8115-b8227ae9f9a3@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 8/17/16 8:12 AM, Andrew Gierth wrote:
> I also recently found a case where using btree exclusion constraints was
> useful: a unique index on an expression can't be marked deferrable, but
> the equivalent exclusion constraint can be.
That seems well worth documenting...
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532) mobile: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2016-08-20 00:13:42 | Re: LSN as a recovery target |
| Previous Message | Tom Lane | 2016-08-19 23:22:02 | Re: Re: PROPOSAL: make PostgreSQL sanitizers-friendly (and prevent information disclosure) |