| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ruslan A Dautkhanov <rusland(at)scn(dot)ru> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Serialize transactions |
| Date: | 2003-01-05 04:47:52 |
| Message-ID: | 6415.1041742072@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Ruslan A Dautkhanov <rusland(at)scn(dot)ru> writes:
> I have sometimes (rarely, once per some days) error during
> executting different queries in PostgreSQL:
> ERROR: Can't serialize access due to concurrent update
> All my transactions use
> SET TRANSACTION ISOLATION LEVEL SERIALIZABLE
If you use serializable mode for updating transactions, you must expect
this error and deal with it (by retrying the transaction from the top).
This is discussed in the documentation, eg at
http://www.ca.postgresql.org/users-lounge/docs/7.3/postgres/transaction-iso.html#XACT-SERIALIZABLE
You might also find it useful to go through the slides from this talk:
http://conferences.oreillynet.com/cs/os2002/view/e_sess/2681
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | pgsql-bugs | 2003-01-05 20:38:16 | Bug #864: MOD(RANDOM(),1.0) don't work in 7.3.1 |
| Previous Message | Ruslan A Dautkhanov | 2003-01-05 04:08:10 | Serialize transactions |