Re: [PATCH] lock_timeout and common SIGALRM framework - Mailing list pgsql-hackers

From Andres Freund
Subject Re: [PATCH] lock_timeout and common SIGALRM framework
Date
Msg-id 20121208143031.GB13557@awork2.anarazel.de
Whole thread Raw
In response to Re: [PATCH] lock_timeout and common SIGALRM framework  (Boszormenyi Zoltan <zb@cybertec.at>)
Responses Re: [PATCH] lock_timeout and common SIGALRM framework  (Boszormenyi Zoltan <zb@cybertec.at>)
List pgsql-hackers
On 2012-10-18 22:40:15 +0200, Boszormenyi Zoltan wrote:
> 2012-10-18 20:08 keltezéssel, Tom Lane írta:
> >Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> >>Boszormenyi Zoltan escribió:
> >>>this is the latest one, fixing a bug in the accounting
> >>>of per-statement lock timeout handling and tweaking
> >>>some comments.
> >>Tom, are you able to give this patch some more time on this commitfest?
> >I'm still hoping to get to it, but I've been spending a lot of time on
> >bug fixing rather than patch review lately :-(.  If you're hoping to
> >close out the current CF soon, maybe we should just slip it to the next
> >one.
>
> Fine by me. Thanks.

According to this the current state of the patch should be "Ready for
Committer" not "Needs Review" is that right? I changed the state for
now...

Greetings,

Andres Freund

--Andres Freund                       http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: PATCH: optimized DROP of multiple tables within a transaction
Next
From: Tom Lane
Date:
Subject: Re: Support for REINDEX CONCURRENTLY