Re: FOREIGN KEY and AccessExclusiveLock

Поиск
Список
Период
Сортировка
От Achilleus Mantzios
Тема Re: FOREIGN KEY and AccessExclusiveLock
Дата
Msg-id Pine.LNX.4.44.0409291611520.704-100000@matrix.gatewaynet.com
обсуждение исходный текст
Ответ на FOREIGN KEY and AccessExclusiveLock  (Achilleus Mantzios <achill@matrix.gatewaynet.com>)
Ответы Re: FOREIGN KEY and AccessExclusiveLock  (Achilleus Mantzios <achill@matrix.gatewaynet.com>)
Список pgsql-sql
Hmm, (something went wrong with some mailer)

Tom Lane wrote:
> We're adding a trigger to it.

From the docs:
============================================================================
ACCESS EXCLUSIVE
Conflicts with locks of all modes (ACCESS SHARE, ROW SHARE, ROW 
EXCLUSIVE, SHARE UPDATE EXCLUSIVE, SHARE, SHARE ROW EXCLUSIVE, EXCLUSIVE, 
and ACCESS EXCLUSIVE). This mode guarantees that the holder is the only 
transaction accessing the table in any way. 


Acquired by the ALTER TABLE, DROP TABLE, REINDEX, CLUSTER, and VACUUM FULL 
commands. This is also the default lock mode for LOCK TABLE statements 
that do not specify a mode explicitly. 


Tip: Only an ACCESS EXCLUSIVE lock blocks a SELECT (without FOR UPDATE) 
statement. 
============================================================================

Now, is the lock acquired for the CREATE TRIGGER an explicit
LOCK TABLE?
Because nothing is mentioned about triggers in 
http://www.postgresql.org/docs/7.4/interactive/explicit-locking.html
-- 
-Achilleus



В списке pgsql-sql по дате отправления:

Предыдущее
От: Paulo Nievierowski
Дата:
Сообщение: SELECT with Function
Следующее
От: van Elsacker Frans
Дата:
Сообщение: multiple insert