| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
| Cc: | Kevin Grittner <kgrittn(at)gmail(dot)com>, Vitaly Burovoy <vitaly(dot)burovoy(at)gmail(dot)com>, Peter Geoghegan <peter(dot)geoghegan86(at)gmail(dot)com>, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, Jason Dusek <jason(dot)dusek(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: SERIALIZABLE and INSERTs with multiple VALUES |
| Date: | 2016-10-12 20:07:32 |
| Message-ID: | CAH2-WzmjYyGY=vK2Q8CPy-qG2TQkMDVT3BH8rhKuh1HLG=dauQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Oct 12, 2016 at 1:05 PM, Thomas Munro
<thomas(dot)munro(at)enterprisedb(dot)com> wrote:
> Here's a patch that shows one way to fix it. I think it does make
> sense to change this, because otherwise automatic
> retry-on-serialization-failure strategies will be befuddle by this
> doomed transaction. And as you and Vitaly have said, there is
> literally no concurrent update.
I think that you have the right idea, but we still need to fix that
buffer lock bug I mentioned...
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2016-10-12 20:41:41 | Re: SERIALIZABLE and INSERTs with multiple VALUES |
| Previous Message | Thomas Munro | 2016-10-12 20:05:52 | Re: SERIALIZABLE and INSERTs with multiple VALUES |