| From: | Evan Jones <ej(at)evanjones(dot)ca> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: PG Manual: Clarifying the repeatable read isolation example |
| Date: | 2014-05-27 19:38:35 |
| Message-ID: | 9E7DE655-624A-48F6-BC87-89673DEC1E58@evanjones.ca |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Oh yeah, I shared an office with Dan so I should have thought to check their paper. Oops. Thanks for the suggestion; I'll try to summarize this into something that is similar to the Read Committed and Serializable mode examples. It may take me a week or two to find the time, but thanks for the suggestions.
Evan
On May 27, 2014, at 15:32 , Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> wrote:
> I agree that's too terse. I think it would be good to actually spell out a complete example of the Receipt problem in the manual. That chapter in the manual contains examples of anomalities in Read Committed mode, so it would be good to give a concrete example of an anomaly in Repeatable Read mode too. Want to write up a docs patch?
--
Work: https://www.mitro.co/ Personal: http://evanjones.ca/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2014-05-27 19:53:53 | json casts |
| Previous Message | Fabrízio de Royes Mello | 2014-05-27 19:36:27 | Re: pg_llog not mentioned in "Database File Layout" |