From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
---|---|
To: | "Bruce Momjian" <bruce(at)momjian(dot)us> |
Cc: | "<Markus Wanner" <markus(at)bluegap(dot)ch>, "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(dot)com>, "Greg Stark" <stark(at)enterprisedb(dot)com>, "Jeff Davis" <pgsql(at)j-davis(dot)com>, "<pgsql-hackers(at)postgresql(dot)org>" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: User-facing aspects of serializable transactions |
Date: | 2009-06-04 15:32:22 |
Message-ID: | 4A27A2B60200002500027503@gw.wicourts.gov |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Added to TODO:
>
> Consider improving serialized transaction behavior to avoid
> anomalies
>
> *
http://archives.postgresql.org/pgsql-hackers/2009-05/msg01136.php
> *
http://archives.postgresql.org/pgsql-hackers/2009-06/msg00035.php
It might be worth adding this reference, too, since it gets down to
some possible implementation techniques:
http://archives.postgresql.org/pgsql-hackers/2009-05/msg00217.php
I was going to try to scare up some resources to advance this if we
could get to some consensus. I don't get the feeling we're there yet.
Suggestions welcome.
-Kevin
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2009-06-04 15:35:46 | Re: PANIC: corrupted item lengths |
Previous Message | Andrew Dunstan | 2009-06-04 14:52:50 | Re: It's June 1; do you know where your release is? |