| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, drkp(at)csail(dot)mit(dot)edu, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: SSI, simplified |
| Date: | 2011-01-26 18:02:10 |
| Message-ID: | 4D4061A2.40007@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 26.01.2011 17:00, Kevin Grittner wrote:
> Simon Riggs<simon(at)2ndQuadrant(dot)com> wrote:
>
>> So in the Compatibility release notes for 9.1 we should say:
>>
>> "Applications that request SERIALIZABLE mode will now experience
>> different and fully correct behaviour. The new mode does not
>> currently work in Hot Standby mode, and an error will be returned
>> if this is requested. If the previous serializable behaviour is
>> required, users should request transaction isolation mode
>> REPEATABLE READ."
>
> Yeah, we definitely need to mention it in the release notes. I feel
> there should also be notes in the regular docs, but Heikki would
> (quite understandably) prefer to minimize changes to the current
> patch until it is committed and deal with that such issues in
> smaller follow-up patches.
By all means, feel free to add a note to the docs about this. A note in
the Hot Standby Caveats section would be good, in addition to somewhere
in the chapter about isolation levels.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2011-01-26 18:06:13 | Re: SSI, simplified |
| Previous Message | Cristiano Duarte | 2011-01-26 17:50:43 | Explain with schema |