Skip site navigation (1) Skip section navigation (2)

Re: default_transaction_isolation = serializable causes crash under Hot Standby

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Robert Haas" <robertmhaas(at)gmail(dot)com>
Cc: <pgsql-hackers(at)postgresql(dot)org>,<tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: default_transaction_isolation = serializable causes crash under Hot Standby
Date: 2012-04-30 14:26:19
Message-ID: 4F9E5ABB0200002500047590@gw.wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-hackers
Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
 
>> * throw a WARNING if serializable is stated in other cases, and
>> downgrade the request to repeatable read
> 
> I think this would be reasonable, but it's still my second choice.
> The advantage of throwing an ERROR is that someone will presumably
> be forced to realize that a problem exists and fix it, whereas a
> WARNING may just generate a combination of log spam and unexpected
> behavior forever.  Also, we currently block cases where you try to
> set transaction_isolation by throwing an ERROR, so it seems a bit
> more consistent to do that in other cases as well.  Still, it's a
> reasonable choice, and certainly better than failing an assertion.
 
I'm not totally clear on your first choice.  Are you looking for
something similar to the patch I posted, except that it would dodge
all resulting errors at the point where they are promoted to FATAL
(before HS is really functional)?
 
-Kevin

In response to

Responses

pgsql-hackers by date

Next:From: Robert HaasDate: 2012-04-30 14:56:38
Subject: Re: default_transaction_isolation = serializable causes crash under Hot Standby
Previous:From: Tom LaneDate: 2012-04-30 14:24:30
Subject: Re: Analyzing foreign tables & memory problems

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group