Re: Serialization errors despite KEY SHARE/NO KEY UPDATE

From: Olivier Dony <odo+pggen(at)odoo(dot)com>
To: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>, Kevin Grittner <kgrittn(at)ymail(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Serialization errors despite KEY SHARE/NO KEY UPDATE
Date: 2015-10-15 07:48:38
Message-ID: 561F5A56.2000304@odoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 10/12/2015 03:59 PM, Jim Nasby wrote:
> On 10/6/15 12:18 PM, Olivier Dony wrote:
>>
>> We would happily skip the micro-transactions (as a perf workaround) if
>> there was a way to detect this situation, but we couldn't find a way to
>> do that in 9.3. <9.3 we used SELECT FOR UPDATE NOWAIT to guard similar
>> cases.
>>
>> If there is any way I could help to make the back-patch happen, please
>> let me know!
>
> I'd say you should probably open a bug about this to make sure it's
> visible if you want it fixed. Or start a thread on -hackers.

Good point, I've submitted bug #13681, thanks! :-)

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Dario Beraldi 2015-10-15 10:21:58 Installing plpython3u
Previous Message Lele Gaifax 2015-10-15 06:48:35 Re: Understanding "seq scans"