| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | gzoller(at)hotmail(dot)com (Greg Zoller) |
| Cc: | pgsql-general(at)postgreSQL(dot)org |
| Subject: | Re: Row-Level Locking? |
| Date: | 2001-05-23 19:23:48 |
| Message-ID: | 16539.990645828@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-jdbc |
gzoller(at)hotmail(dot)com (Greg Zoller) writes:
> My problem is this: what happens if half-way through this set of
> operations someone else (perhaps in another thread) attempts to execute
> the same operation?
See
http://www.ca.postgresql.org/users-lounge/docs/7.1/postgres/mvcc.html
SELECT FOR UPDATE and/or the implicit row lock done by UPDATE should
solve your problem.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-05-23 19:25:44 | Re: NOTIFY/LISTEN Using Embedded SQL (ecpg) |
| Previous Message | Tom Lane | 2001-05-23 19:19:40 | Re: incomplete transaction keeps table locked? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2001-05-23 19:30:03 | ANT fix for jar creation |
| Previous Message | Tony Grant | 2001-05-23 13:39:56 | Re: Unicode problems. |