Prev: [HACKERS] Trigger function in a multi-threaded environment behavior
Next: Trigger function in a multi-threaded environment behavior
From: Peter Eisentraut on 1 Jun 2010 07:27
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.




--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

 | 
Pages: 1
Prev: [HACKERS] Trigger function in a multi-threaded environment behavior
Next: Trigger function in a multi-threaded environment behavior