Skip site navigation (1) Skip section navigation (2)

Re: User-facing aspects of serializable transactions

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Greg Stark <greg(dot)stark(at)enterprisedb(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Jeff Davis <pgsql(at)j-davis(dot)com>
Subject: Re: User-facing aspects of serializable transactions
Date: 2009-05-28 16:21:06
Message-ID: 11392.1243527666@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Robert Haas <robertmhaas(at)gmail(dot)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.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Robert HaasDate: 2009-05-28 16:21:49
Subject: Re: PostgreSQL Developer meeting minutes up
Previous:From: Tom LaneDate: 2009-05-28 16:19:39
Subject: Re: PostgreSQL Developer meeting minutes up

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group