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: "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: default_transaction_isolation = serializable causes crash under Hot Standby
Date: 2012-04-27 15:24:42
Message-ID: 4F9A73EA0200002500047466@gw.wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-hackers
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> Or, maybe there's a way to throw an error when serializable mode
>> is used rather than when it's requested.
> 
> Couldn't we check and throw an error at the place in transaction
> startup where default_transaction_isolation is copied to the
> active variable?
 
Wouldn't that leave users stuck if the postgresql.conf set the
default to serializable?  Nobody would be able to start a
transaction, even to change the default, would they?  If that's the
case, we might as well refuse to start.
 
Robert's suggestion might be the least of the various evils.
 
-Kevin

In response to

Responses

pgsql-hackers by date

Next:From: Thom BrownDate: 2012-04-27 15:41:01
Subject: Re: enable_indexonly
Previous:From: Simon RiggsDate: 2012-04-27 15:08:00
Subject: enable_indexonly

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