| From: | seth(dot)m(dot)green(at)gmail(dot)com |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | ACCESS EXCLUSIVE LOCK |
| Date: | 2006-03-01 23:55:26 |
| Message-ID: | 1141257326.931828.65520@e56g2000cwe.googlegroups.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
This may be a newbie question, but according to the 7.4 docs, an ACCESS
EXCLUSIVE lock is only acquired by the ALTER TABLE, DROP TABLE,
REINDEX, CLUSTER, and VACUUM FULL commands.
However, when viewing pg_locks during the execution of a stored
procedure that does not perform any of the above commands, I see that
the table it is working on is locked by ACCESS EXCLUSIVE.
I have also tested that I can not perform a simple SELECT on the locked
table while the SP is executing.
Can anyone provide some insight?
Thanks
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-03-01 23:58:25 | Re: [SQL] Interval subtracting |
| Previous Message | Mark Dilger | 2006-03-01 23:49:46 | Re: [SQL] Interval subtracting |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-03-01 23:58:25 | Re: [SQL] Interval subtracting |
| Previous Message | Mark Dilger | 2006-03-01 23:49:46 | Re: [SQL] Interval subtracting |