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

Re: default_transaction_isolation = serializable causes crash under Hot Standby

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: robertmhaas(at)gmail(dot)com, 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-29 17:33:00
Message-ID: CA+U5nMLmyQbQ5-SpE3MAC-DdkZgzC8vFCTtDXjP9YUuYfjimPA@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Sun, Apr 29, 2012 at 5:54 PM, Kevin Grittner
<Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> Simon Riggs  wrote:
>
>> The only way default_transaction_isolation = serializable would be
>> acceptable when hot_standby = on is if we silently downgrade the
>> isolation level to read committed. That way everything just works,
>> albeit not quite as requested. So I think that's the best way
>> forwards.
>
> I guess I don't see much alternative.  Did you want to code that (I
> seem to remember you saying that in an earlier post) or would you
> like me to do it?

I'll happily do that, unless you wish to.

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

In response to

pgsql-hackers by date

Next:From: Peter EisentrautDate: 2012-04-29 17:48:26
Subject: Re: smart shutdown at end of transaction (was: Default mode for shutdown)
Previous:From: Simon RiggsDate: 2012-04-29 17:28:49
Subject: Re: Future In-Core Replication

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