Re: Serialization exception : Who else was involved?

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To: Olivier MATROT <olivier(dot)matrot(at)accelis-sir(dot)fr>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Serialization exception : Who else was involved?
Date: 2014-12-27 10:02:48
Message-ID: 549E83C8.4000207@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12/02/2014 06:17 PM, Olivier MATROT wrote:
> Serialization conflict detection is done in
> *src/backend/storage/lmgr/predicate.c*, where transactions that are
> doomed to fail are marked as such with *the SXACT_FLAG_DOOMED* flag.
>
> I simply added elog(...) calls with the NOTIFY level, each time the flag
> is set, compiled the code and give it a try.

I don't see how that'd necessarily correctly identify the query/queries
in the other tx that're involved, though.

Perhaps I'm thinking in terms of more complicated serialization
failures? What sorts of failures are you actually running into?

--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2014-12-27 15:10:34 Re: CATUPDATE confusion?
Previous Message Craig Ringer 2014-12-27 09:58:40 Re: Serialization exception : Who else was involved?