Re: [PATCH] pg_sleep(interval)

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Vik Fearing <vik(dot)fearing(at)dalibo(dot)com>
Cc: PG Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] pg_sleep(interval)
Date: 2013-10-16 08:57:44
Message-ID: alpine.DEB.2.02.1310161051420.11284@sto
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Hello Vik,

>> Yes, I understand you are trying to help, and I appreciate it! My
>> opinion, and that of others as well from the original thread, is that
>> this patch should either go in as is and break that one case, or not go
>> in at all. I'm fine with either (although clearly I would prefer it
>> went in otherwise I wouldn't have written the patch).
>
> I see this is marked as rejected in the commitfest app, but I don't see
> any note about who did it or why. I don't believe there is consensus
> for rejection on this list. In fact I think the opposite is true.
>
> May we have an explanation please from the person who rejected this
> without comment?

I did it, on the basis that you stated that you prefered not adding
pg_sleep(TEXT) to answer Robert Haas concern about preserving
pg_sleep('10') current functionality, and that no other solution was
suggested to tackle this issue.

If I'm mistaken, feel free to change the state back to what is
appropriate.

My actual opinion is that breaking pg_sleep('10') is no big deal, but I'm
nobody here, and Robert is somebody, so I think that his concern must be
addressed.

--
Fabien.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Vik Fearing 2013-10-16 09:19:27 Re: [PATCH] pg_sleep(interval)
Previous Message Ronan Dunklau 2013-10-16 06:33:14 Re: Triggers on foreign tables