| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Michael Fuhr <mike(at)fuhr(dot)org> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Sleep functions |
| Date: | 2005-08-21 23:24:03 |
| Message-ID: | 43090D13.20008@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Michael Fuhr wrote:
>What do people think of exposing pg_usleep() to the user? It's
>sometimes useful to have a server-side sleep function, and people
>do ask about it occasionally (e.g., Don Drake today in pgsql-admin).
>It's easy enough to do in PL/Perl, PL/Tcl, etc., but since the
>backend already has pg_usleep(), is there any reason not to expose
>it? I'd propose both sleep() and usleep() functions.
>
>
Be careful with documentation - IIRC on Windows the granularity of the
Sleep() function is 1 millisec and pg_usleep rounds to the nearest
millisec except for very low values where it rounds up.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2005-08-21 23:28:25 | Re: Sleep functions |
| Previous Message | Hannu Krosing | 2005-08-21 23:14:23 | Re: Missing CONCURRENT VACUUM (Was: Release notes for |