Re: [HACKERS] [GENERAL] Solution to UPDATE...INSERT problem

2003-04-03 Thread Lincoln Yeoh
AFAIK the "except" select won't see other inserts in uncommitted transactions. If those transactions are committed you will end up with the same problem. You can try it yourself, by manually doing two separate transactions in psql. You either have to lock the whole table, or lock at the applica

Re: [HACKERS] [GENERAL] Solution to UPDATE...INSERT problem

2003-04-03 Thread Dennis Gearon
so the only real solution to this now is in application code outside of a transatction, i.e. PHP,Perl,VB,C,Python, etc, right? Lincoln Yeoh wrote: AFAIK the "except" select won't see other inserts in uncommitted transactions. If those transactions are committed you will end up with the same pro

Re: [HACKERS] [GENERAL] Solution to UPDATE...INSERT problem

2003-04-03 Thread Lincoln Yeoh
At 05:28 PM 3/27/03 +0800, Christopher Kings-Lynne wrote: > There's no "select * from table where pkey=x for insert;" which would block > on uncommitted inserts/updates of pkey=x and other selects for insert/update. How about user locks? Isn't there something in contrib/ for that??? I could do a

Re: [HACKERS] [GENERAL] Solution to UPDATE...INSERT problem

2003-03-27 Thread Christopher Kings-Lynne
> AFAIK the "except" select won't see other inserts in uncommitted > transactions. If those transactions are committed you will end up with the > same problem. You can try it yourself, by manually doing two separate > transactions in psql. Yeah, I see that now. > You either have to lock the whole