| From: | "Michael P(dot) Soulier" <michael_soulier(at)mitel(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Misunderstanding transactions and locks |
| Date: | 2010-06-18 02:08:09 |
| Message-ID: | 20100618020809.GU26066@e-smith.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 16/06/10 Tom Lane did say:
> > "row exclusive mode" does not block itself.
>
> Specifically, see the table in
> http://www.postgresql.org/docs/8.3/static/explicit-locking.html#LOCKING-TABLES
>
> Exclusive lock modes are those that conflict with themselves; to wit,
> SHARE ROW EXCLUSIVE mode or higher. The mode names are, um, historical.
That explains much.
Thanks,
Mike
--
Michael P. Soulier <michael_soulier(at)mitel(dot)com>, 613-592-2122 x2522
"Any intelligent fool can make things bigger and more complex... It takes a
touch of genius - and a lot of courage to move in the opposite direction."
--Albert Einstein
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Felde Norbert | 2010-06-18 08:55:09 | Re: postgres crash SOS |
| Previous Message | Joshua D. Drake | 2010-06-18 02:04:39 | Re: UUID/GUID |