Re: update functions locking tables - Mailing list pgsql-general

From Clodoaldo Pinto
Subject Re: update functions locking tables
Date
Msg-id a595de7a05083006016be6189@mail.gmail.com
Whole thread Raw
In response to Re: update functions locking tables  (Michael Fuhr <mike@fuhr.org>)
List pgsql-general
2005/8/30, Michael Fuhr <mike@fuhr.org>:
>
> TRUNCATE acquires an AccessExclusiveLock, which conflicts with all
> other lock types.  Locks are held until the transaction completes,
> so once this lock is acquired no other transactions will be able
> to access the table until this transaction commits or rolls back.
>
> DELETE is slower than TRUNCATE but it won't block readers in other
> transactions.
>

I think it is of great help. I will change it and let you know what happened.

Regards, Clodoaldo Pinto

pgsql-general by date:

Previous
From: Bruno Wolff III
Date:
Subject: Re: Planner create a slow plan without an available index
Next
From: Greg Stark
Date:
Subject: Re: About dropped notifications