Greg Sabino Mullane wrote
> Disabling triggers requires a heavy lock. A better way is to use
> the session_replication_role feature. See:
>
> http://blog.endpoint.com/2015/01/postgres-sessionreplication-role.html
This is a very effective solution to my problem. Thanks for the tip, Greg.
--
Vi
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> I'm doing some maintenance - which is done quite often, never had this
> problem before - which requires me to disable triggers, run some updates and
> then re-enable the triggers.
Disabling triggers requires a heavy lock. A better way is to
David Steele wrote
>
> ALTER TABLE requires an exclusive lock - my guess is that another
> process has a lock on the table. It could even be a select.
>
> pg_locks is your friend in this case:
> http://www.postgresql.org/docs/9.4/static/view-pg-locks.html
Hi David
I'm a bit confused on how to
On 2/27/15 9:07 AM, gmb wrote:
> Hi all
>
> I'm doing some maintenance - which is done quite often, never had this
> problem before - which requires me to disable triggers, run some updates and
> then re-enable the triggers.
> Where the whole process normally take 30 sec , it took much longer tod
binK_rPgnIklP.bin
Description: charset
Hi all
I'm doing some maintenance - which is done quite often, never had this
problem before - which requires me to disable triggers, run some updates and
then re-enable the triggers.
Where the whole process normally take 30 sec , it took much longer today and
I cancelled after 5 minutes.
After
