| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> |
| Cc: | "Warren Volz" <wrv(at)po(dot)cwru(dot)edu>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Bug #514: Backend crashes periodically |
| Date: | 2001-11-14 15:26:09 |
| Message-ID: | 6522.1005751569@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> writes:
> The problem is that session 2 sees a not yet deleted( by session 1)
> session row and an already updated( by session 1) sis_user row at
> the same time. There's no such snapshot that could see both rows.
Running in SERIALIZABLE mode would guarantee consistency, no?
(Session 2 would be forced to roll back and try again, and when
it tried again it would see the session row already gone.)
I doubt that there is any lesser answer that guarantees consistency
across multiple queries.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-11-14 15:40:29 | Re: Bug #515: REVOKE delete set select grant to user |
| Previous Message | pgsql-bugs | 2001-11-14 14:51:07 | Bug #515: REVOKE delete set select grant to user |