pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim Nasby <Jim.Nasby@BlueTreble.com>
To: Olivier Dony <odo+pggen@odoo.com>
To: Kevin Grittner <kgrittn@ymail.com>
Cc: pgsql-general@postgresql.org <pgsql-general@postgresql.org>
Subject: Re: Serialization errors despite KEY SHARE/NO KEY UPDATE
Date: Mon, 12 Oct 2015 08:59:44 -0500
Message-ID: <561BBCD0.1060301@BlueTreble.com> (raw)
In-Reply-To: <5614026C.10404@odoo.com>
References: <560ED745.3050009@BlueTreble.com>
	<1354271993.744124.1444079872314.JavaMail.yahoo@mail.yahoo.com>
	<5614026C.10404@odoo.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-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


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general



view thread (8+ messages)  latest in thread

Message-ID: <561BBCD0.1060301@BlueTreble.com>
Permalink:  ../561BBCD0.1060301@BlueTreble.com/
Also on:    postgresql.org/message-id/561BBCD0.1060301@BlueTreble.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-general@postgresql.org
  Cc: Jim.Nasby@BlueTreble.com, odo+pggen@odoo.com, kgrittn@ymail.com
  Subject: Re: Serialization errors despite KEY SHARE/NO KEY UPDATE
  In-Reply-To: <561BBCD0.1060301@BlueTreble.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox