Search Postgresql Archives

Re: getting lock information

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"Qingqing Zhou" <zhouqq@xxxxxxxxxxxxxx> writes:
>> "Himanshu Baweja" <himanshubaweja@xxxxxxxxx> 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-related events :-(

			regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@xxxxxxxxxxxxxx

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux