Re: Select For Update and Left Outer Join

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: Patrick Earl <patearl(at)patearl(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Select For Update and Left Outer Join
Date: 2011-07-11 15:58:05
Message-ID: 4E1B1D8D.6010606@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 11.07.2011 18:44, Kevin Grittner wrote:
> (In our in-house
> testing I've so far found one place where we needed to take an
> explicit lock on a dummy table we created just to control access to
> a sequence -- sequences don't follow normal transactional
> semantics.)

Hmm, is that something we should do something about? Can you give an
example of that?

Not in 9.1, except in the docs if we don't mention that already, but in
the future...

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2011-07-11 15:58:20 remove README.mb.jp and README.mb.big5?
Previous Message Peter Eisentraut 2011-07-11 15:48:22 Re: Full GUID support