| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Florian Pflug <fgp(at)phlo(dot)org> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Row-level Locks & SERIALIZABLE transactions, postgres vs. Oracle |
| Date: | 2010-05-14 00:37:27 |
| Message-ID: | AANLkTinRIpEFSkVG-u_6U2wGCfQ9_DJ-D9sU0E9BL33Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, May 13, 2010 at 10:25 PM, Florian Pflug <fgp(at)phlo(dot)org> wrote:
> C1: BEGIN
> C1: SELECT * FROM t WHERE id = 1 FOR UPDATE
> C2: BEGIN
> C2: SET TRANSACTION ISOLATION LEVEL SERIALIZABLE
> C2: SELECT * FROM t -- Take snapshot before C1 commits
> C1: COMMIT
> C2: DELETE FROM t WHERE id = 1
> C2: COMMIT
>
Can you give an actual realistic example -- ie, not doing a select for
update and then never updating the row or with an explanation of what
the programmer is attempting to accomplish with such an unusual
sequence? The rest of the post talks about FKs but I don't see any
here...
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-05-14 01:01:55 | Re: pg_upgrade code questions |
| Previous Message | Bruce Momjian | 2010-05-14 00:23:33 | Re: Re: [COMMITTERS] pgsql: Add PGFILEDESC description to Makefiles for all /contrib |