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 603c8f070905281007g16a6a4cfub999f63eb441a7fd@mail.gmail.com
Whole thread Raw
In response to Re: User-facing aspects of serializable transactions  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, May 28, 2009 at 12:21 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> What's hard about that?  INSERTs are the hard case, because the rows
>> you care about don't exist yet.  SELECT, UPDATE, and DELETE are easy
>> by comparison; you can lock the actual rows at issue.  Unless I'm
>> confused?
>
> UPDATE isn't really any easier than INSERT: the update might cause
> the row to satisfy someone else's search condition that it didn't
> previously satisfy.

Good point.

...Robert


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: PostgreSQL Developer meeting minutes up
Next
From: Stephen Frost
Date:
Subject: Re: PostgreSQL Developer meeting minutes up