Re: lock_timeout GUC patch - Review

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Boszormenyi Zoltan" <zb(at)cybertec(dot)at>, "Marc Cousin" <cousinmarc(at)gmail(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: lock_timeout GUC patch - Review
Date: 2010-08-02 19:09:19
Message-ID: 4C56D18F0200002500034089@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Marc Cousin <cousinmarc(at)gmail(dot)com> wrote:

> This time, it's this case that doesn't work :

> I really feel that the timeout framework is the way to go here.

Since Zoltán also seems to feel this way:

http://archives.postgresql.org/message-id/4C516C3A.6090102@cybertec.at

I wonder whether this patch shouldn't be rejected with a request
that the timeout framework be submitted to the next CF. Does anyone
feel this approach (without the framework) should be pursued
further?

-Kevin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Boszormenyi Zoltan 2010-08-02 19:52:42 Re: lock_timeout GUC patch - Review
Previous Message Yeb Havinga 2010-08-02 18:56:48 Re: patch for check constraints using multiple inheritance