Re: Forcibly vacating locks

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Laurent Birtz <laurent(dot)birtz(at)kryptiva(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Forcibly vacating locks
Date: 2008-06-20 22:38:23
Message-ID: 200806202238.m5KMcN616018@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2008-06-20 23:54:24 Re: Timezone issue - Is it me or is this a massive bug?
Previous Message Collin Peters 2008-06-20 20:19:13 Timezone issue - Is it me or is this a massive bug?