| From: | Markus Schaber <schabi(at)logix-tt(dot)com> |
|---|---|
| To: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Changing the transaction isolation level within the stored |
| Date: | 2006-02-02 14:19:26 |
| Message-ID: | 43E214EE.3090005@logix-tt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Hi, Andreq,
Andrew Sullivan wrote:
> I think you don't have a clear idea of what locks are necessary for
> updates. Write operations on a row must block other write operations
> on the same row. If more than one transaction needs the same kinds
> of locks on two different tables, but attempts to get those locks in
> the opposite order, you are all but guaranteed a deadlock. MVCC
> helps, but it can't avoid locking the same data when that data is
> being updated.
You're right, I was mislead from my memory.
Sorry for the confusion I brought to this issue.
Markus
--
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf. | Software Development GIS
Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Markus Schaber | 2006-02-02 14:25:32 | Re: Does PostgreSQL support job? |
| Previous Message | Daniel Caune | 2006-02-02 14:19:25 | Re: Does PostgreSQL support job? |