| From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)2ndquadrant(dot)com> |
| Subject: | Re: Promise index tuples for UPSERT |
| Date: | 2014-10-03 10:54:02 |
| Message-ID: | 542E804A.4070504@vmware.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10/03/2014 01:05 PM, Peter Geoghegan wrote:
> On Fri, Oct 3, 2014 at 3:04 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>> Is there a test case that demonstrates the problem?
>
> Yes. See my e-mail to Heikki here:
>
> http://www.postgresql.org/message-id/CAM3SWZShbE29KpoD44cVc3vpZJGmDer6k_6FGHiSzeOZGmTFSQ@mail.gmail.com
>
> Testcase is attached.
Simon's approach would actually pass that test case just fine. It
inserts the (promise) index tuple first, and heap tuple only after that.
It will fail the test case with more than one unique index, however.
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2014-10-03 11:55:06 | Re: GiST splitting on empty pages |
| Previous Message | Peter Geoghegan | 2014-10-03 10:05:57 | Re: Promise index tuples for UPSERT |