| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Gabriel Fernandez <gabi(at)unica(dot)edu> |
| Cc: | PostgreSQL-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: [GENERAL] Confussion with table-lock levels and isolation levels |
| Date: | 2000-01-16 17:13:46 |
| Message-ID: | Pine.LNX.4.21.0001151955470.386-100000@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2000-01-13, Gabriel Fernandez mentioned:
> - What does exactly mean that a mode 'CONFLICTS' with another
> ?
> - Does it mean that another concurrent transactions having
> these modes will have to wait until the first transaction
> have finished (commit or roll back) ?
Yes. You can try that pretty easily. Start up two psqls, in the first one
enter:
BEGIN TRANSACTION;
LOCK pg_class IN ACCESS EXCLUSIVE MODE;
In the second one enter:
SELECT * FROM pg_class;
The latter will hang.
--
Peter Eisentraut Sernanders väg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2000-01-16 17:13:51 | Re: Oids vs Serial fields (was Re: [GENERAL] searching oid's) |
| Previous Message | Peter Eisentraut | 2000-01-16 17:13:40 | Re: [GENERAL] PSQL Function() help.... |