Search Postgresql Archives

Re: Forcibly vacating locks

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

 



Laurent Birtz wrote:
> > No.  The closest thing we have is log_lock_waits in 8.3.  I wonder if
> > you could hack up something to monitor the server logs for such messages
> > and cancel the queries.
> 
> Assuming I can monitor the logs in this way, how would I cancel the 
> queries (or lack thereof, in the case of a client that sits doing nothing
> with a held lock)?

Use log_line_prefix to get the process id in the log line, then use
pg_cancel_backend() on the process id.

> >> 2) Is there any hostility about the notion of implementing this feature
> >>     into Postgres?
> > 
> > Probabably --- it seems like a narrow use case.
> 
> I'll consider this to be the definite answer unless I hear a dissenting
> opinion in the next few days.

Yea, I might be wrong.

-- 
  Bruce Momjian  <bruce@xxxxxxxxxx>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +


[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