From: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Lock ACCESS EXCLUSIVE and Select question ! |
Date: | 2011-02-28 22:59:29 |
Message-ID: | 20110228225928.GC80597@shinkuro.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Feb 28, 2011 at 05:39:07PM -0500, Alan Acosta wrote:
> But i have a new problem there, i have no rows for update, i create new rows
> when the seats are sold, cause rarely the database knows the capacity of the
> bus, number of seats, even some bus doesn't have seat number 4 for example
> :p. So i cannot SELECT FOR UPDATE no existent rows, but i still need to lock
> in some way in order to check if seat number X was already sold or is free !
Someone else suggests that you need a uniqueness constraint, and I
agree. But I also don't understand how you can be ensuring not to
double-sell something if you don't have the list of inventory prior to
its being sold.
A
--
Andrew Sullivan
ajs(at)crankycanuck(dot)ca
From | Date | Subject | |
---|---|---|---|
Next Message | Gary Fu | 2011-02-28 23:16:14 | Re: slow building index and reference after Sybase to Pg |
Previous Message | Andres Freund | 2011-02-28 22:56:49 | Re: slow building index and reference after Sybase to Pg |