Re: Serializable snapshot isolation patch

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Jeff Davis" <pgsql(at)j-davis(dot)com>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Serializable snapshot isolation patch
Date: 2010-10-21 23:33:12
Message-ID: 4CC087680200002500036C93@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jeff Davis <pgsql(at)j-davis(dot)com> wrote:

> When using locks in an unconventional way, it would be helpful to
> describe the invalid schedules that you're preventing. Perhaps an
> example if you think it would be reasonably simple? Also some
> indication of how another process is intended to modify the list
> without walking it.

I've just pushed some comment changes intended to address this. Did
I hit the mark?

-Kevin

P.S. Sorry for the delay in responding to such simple requests --
I've been tied up with a family medical crisis; I hope to crank
through much of what you've raised this weekend.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2010-10-21 23:49:54 Re: Floating-point timestamps versus Range Types
Previous Message Scott Carey 2010-10-21 23:11:22 Re: Slow count(*) again...