Re: default_transaction_isolation = serializable causes crash under Hot Standby - Mailing list pgsql-hackers

From Robert Haas
Subject Re: default_transaction_isolation = serializable causes crash under Hot Standby
Date
Msg-id CA+TgmoY3mqWO+TbC7zizjGkrzcOD5uXBiqKJr3z-uTp8kbsQOQ@mail.gmail.com
Whole thread Raw
In response to Re: default_transaction_isolation = serializable causes crash under Hot Standby  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: default_transaction_isolation = serializable causes crash under Hot Standby  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, Apr 27, 2012 at 10:21 AM, Kevin Grittner
<Kevin.Grittner@wicourts.gov> wrote:
> My first thought was that if we can detect that we are in HS, we
> should probably throw an ERROR on an attempt to set
> default_transaction_isolation = 'serializable'.

I think that would result in the server failing to start.  We could
throw a warning there and give repeatable read.

Or, maybe there's a way to throw an error when serializable mode is
used rather than when it's requested.  So in the above example SELECT
1; would say, hey, somehow I ended up in serializable mode under HS,
abort, abort!

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Request to add options to tools/git_changelog
Next
From: Tom Lane
Date:
Subject: Re: default_transaction_isolation = serializable causes crash under Hot Standby