| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Greg Stark <stark(at)mit(dot)edu>, Vik Fearing <vik(dot)fearing(at)dalibo(dot)com>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] pg_sleep(interval) |
| Date: | 2013-08-17 00:00:57 |
| Message-ID: | 520EBD39.8060504@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 08/16/2013 04:52 PM, Tom Lane wrote:
> Since the same effect can be had by writing a user-defined SQL function,
> I'm a bit inclined to say that the value-added by having this as a
> built-in function doesn't justify the risk of breaking existing apps.
> It's a close call though, because both the risk and the value-added seem
> rather small from here.
Why not just call it pg_sleep_int()?
I, for one, would find it useful, but would be really unhappy about
about having to debug a bunch of old code to figure out what was broken.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-08-17 00:15:08 | Re: [PATCH] pg_sleep(interval) |
| Previous Message | Michael Cronenworth | 2013-08-16 23:56:45 | Fix Windows socket error checking for MinGW |