From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
---|---|
To: | Olivier Dony <odo+pggen(at)odoo(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-12 13:59:44 |
Message-ID: | 561BBCD0.1060301@BlueTreble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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.
--
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
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2015-10-12 14:15:16 | Re: Drop or alter column under load give ERROR #42804 structure of query does not match function result type: |
Previous Message | Tom Lane | 2015-10-12 13:53:14 | Re: Drop or alter column under load give ERROR #42804 structure of query does not match function result type: |