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

Re: default_transaction_isolation = serializable causes crash under Hot Standby

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: default_transaction_isolation = serializable causes crash under Hot Standby
Date: 2012-04-27 15:05:18
Message-ID: CA+TgmoYXNHK1r8cWeUZNCHY9zOsc8r4LpBGfNX_QQaxpJRhAew@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Fri, Apr 27, 2012 at 11:02 AM, 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?

Yeah, possibly.  Although the user might still use SET TRANSACTION
ISOLATION, so it would ideally be nice to postpone throwing the error
until after that opportunity is past.  Not sure if that's feasible,
though.

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

In response to

pgsql-hackers by date

Next:From: Simon RiggsDate: 2012-04-27 15:08:00
Subject: enable_indexonly
Previous:From: Tom LaneDate: 2012-04-27 15:02:44
Subject: Re: default_transaction_isolation = serializable causes crash under Hot Standby

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