> >> 1) pg_locks ::: need to write trigger... and have
high overhead...
>
> > What do you mean by "write trigger"?
>
> I'm sure he's imagining that he can create a trigger
on pg_locks and
> thereby capture lock-related events :-(
well that was wht i was thinking got it now... i
will recompil
hacking the backend... can u elaborate a little bit
more... i want to write a small utility which other
ppl can use to see when the locks are acquired etc
etc... so that they can optimise their application
using that information... in my application we have
have 4 processes doing almost the same th
Himanshu Baweja wrote:
is there any other better way by which i can get a list of locks
acquired and waited for during entire run of my application
Hacking the backend would be the easiest route, I think. Why do you need
this information -- what are you trying to do?
-Neil
-
"Qingqing Zhou" <[EMAIL PROTECTED]> writes:
>> "Himanshu Baweja" <[EMAIL PROTECTED]> writes
>> 1) pg_locks ::: need to write trigger... and have high overhead...
> What do you mean by "write trigger"?
I'm sure he's imagining that he can create a trigger on pg_locks and
thereby capture lock-relate
>"Himanshu Baweja" <[EMAIL PROTECTED]> writes
>I wanted to see which tables/transaction have acquired or are waiting for
which locks
>as far as i know there are two ways to do it
>
>1) pg_locks ::: need to write trigger... and have high overhead...
>
"select * from pg_locks" has trivial im
I wanted to see which tables/transaction have acquired or are waiting for which locks
as far as i know there are two ways to do it
1) pg_locks ::: need to write trigger... and have high overhead...
2) trace_locks,trace_lwlocks ... etc etc ::: well for this my server says undefined p
