From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | "Robert Haas" <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: default_transaction_isolation = serializable causes crash under Hot Standby |
Date: | 2012-04-27 16:34:31 |
Message-ID: | 22209.1335544471@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> 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?
I was assuming "BEGIN TRANSACTION LEVEL ..." would still work;
if not, it's a non-starter. I haven't looked at the code to see
if the sequence of operations is amenable to that though.
> Robert's suggestion might be the least of the various evils.
Yeah, it would definitely be nicer if BEGIN; SET TRANSACTION LEVEL
would work too. Maybe the place to put the check is where we
establish the transaction snapshot.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2012-04-27 16:42:53 | Re: enable_indexonly |
Previous Message | Andrew Dunstan | 2012-04-27 16:13:04 | Re: A problem with dump/restore of views containing whole row references |