Re: User-facing aspects of serializable transactions - Mailing list pgsql-hackers

From Robert Haas
Subject Re: User-facing aspects of serializable transactions
Date
Msg-id 603c8f070906040916o6c3582c9x1e14be14f3b22cec@mail.gmail.com
Whole thread Raw
In response to Re: User-facing aspects of serializable transactions  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: User-facing aspects of serializable transactions  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers
On Thu, Jun 4, 2009 at 11:32 AM, Kevin Grittner
<Kevin.Grittner@wicourts.gov> wrote:
> 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.

I think I might've said this before, but I think you need to do (or
get someone with knowledge of the code to do) more looking at the lock
bookkeeping that's required to make the SIREAD stuff work and try to
figure out if it's even feasible for PostgreSQL and what the
performance costs would be (an idea of how much code complexity this
would introduce would be good too).  A lot of the "lack of consensus"
at this point looks to me more like "lack of being sure whether this
can actually work".  I don't know that we're going to get any closer
to consensus without some less-handwavy answer to that question.

...Robert


pgsql-hackers by date:

Previous
From: "Kolb, Harald (NSN - DE/Munich)"
Date:
Subject: postmaster recovery and automatic restart suppression
Next
From: Andrew Dunstan
Date:
Subject: Re: It's June 1; do you know where your release is?