Default Access Exclusive Lock on Update?

From: seth(dot)m(dot)green(at)gmail(dot)com
To: pgsql-general(at)postgresql(dot)org
Subject: Default Access Exclusive Lock on Update?
Date: 2006-03-02 12:29:12
Message-ID: 1141302552.210319.245230@i40g2000cwc.googlegroups.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Mary Adel 2006-03-02 12:34:15 php postgresql
Previous Message Ingmar Brouns 2006-03-02 11:38:04 Thread scheduling in postgresql 8.1.3 on windows