From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: Craig James <craig_james@emolecules.com>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: select for update
Date: Fri, 22 Apr 2011 15:25:05 -0500
Message-ID: <4DB19DD1020000250003CC02@gw.wicourts.gov> (raw)
In-Reply-To: <4DB1BFC2.7020806@emolecules.com>
References: <4DB1BFC2.7020806@emolecules.com>
Craig James <craig_james@emolecules.com> wrote:
> The sequence of operations goes like this (pseudo-code):
> The problem is that very occasionally the same ID will be issued
> twice. I don't see how this can be. Doesn't the "for update"
> guarantee that no other process can claim that same row?
I don't see a flaw in the pseudo-code (other than an apparent typo
on the insert). Can you show the actual code?
-Kevin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: Kevin.Grittner@wicourts.gov, craig_james@emolecules.com
Subject: Re: select for update
In-Reply-To: <4DB19DD1020000250003CC02@gw.wicourts.gov>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox