Re: Trigger function in a multi-threaded environment behavior - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Trigger function in a multi-threaded environment behavior
Date
Msg-id 1275391657.15468.4.camel@fsopti579.F-Secure.com
Whole thread Raw
In response to Trigger function in a multi-threaded environment behavior  (Hardik Belani <hardikbelani@gmail.com>)
List pgsql-hackers
On tis, 2010-06-01 at 16:40 +0530, Hardik Belani wrote:

> If we introduce postgres triggers (trigger functions) on some of the
> tables to track insert/update/delete operations, (This is done by
> keeping and updating a counter field for every insert, update and
> delete operation performed on a set of tables inside trigger function)
> at this point, one or more threads get stuck in lock while executing
> the query, to the extent that sometimes even with the pgadmin, the
> database tables cannot be updated.

You should be able to analyze the lock situation using the views
pg_locks and pg_stat_activity.





pgsql-hackers by date:

Previous
From: Hardik Belani
Date:
Subject: Trigger function in a multi-threaded environment behavior
Next
From: Florian Pflug
Date:
Subject: Re: [RFC] A tackle to the leaky VIEWs for RLS