Re: default_transaction_isolation = serializable causes crash under Hot Standby

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: default_transaction_isolation = serializable causes crash under Hot Standby
Date: 2012-04-27 15:00:11
Message-ID: CA+TgmoY3mqWO+TbC7zizjGkrzcOD5uXBiqKJr3z-uTp8kbsQOQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Apr 27, 2012 at 10:21 AM, Kevin Grittner
<Kevin(dot)Grittner(at)wicourts(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2012-04-27 15:02:44 Re: default_transaction_isolation = serializable causes crash under Hot Standby
Previous Message Bruce Momjian 2012-04-27 14:35:01 Re: Request to add options to tools/git_changelog