| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | seth(dot)m(dot)green(at)gmail(dot)com |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: ACCESS EXCLUSIVE LOCK |
| Date: | 2006-03-02 13:43:23 |
| Message-ID: | 20060302134322.GA5404@surnet.cl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
seth(dot)m(dot)green(at)gmail(dot)com wrote:
> 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.
Is the SP executing a LOCK TABLE perchance?
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | seth.m.green | 2006-03-02 13:55:10 | Re: ACCESS EXCLUSIVE LOCK |
| Previous Message | Christopher Browne | 2006-03-02 13:33:46 | Re: Automatic free space map filling |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | seth.m.green | 2006-03-02 13:55:10 | Re: ACCESS EXCLUSIVE LOCK |
| Previous Message | Hannu Krosing | 2006-03-02 09:07:00 | Re: Automatic free space map filling |