Search Postgresql Archives

Re: getting lock information

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

 



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 thing ie they
do the same quey at exactly the same time... and if i
can the complete lock information... i can change the
application so that they dont have to wait for each
other....

thx
Himanshu

--- Neil Conway <neilc@xxxxxxxxxxx> wrote:
> 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
> 


		
__________________________________ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new Resources site
http://smallbusiness.yahoo.com/resources/

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

[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