From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | <mike(at)fuhr(dot)org>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Sleep functions |
Date: | 2005-08-21 23:28:25 |
Message-ID: | 002f01c5a6a8$1306a290$6a01a8c0@valehousing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
-----Original Message-----
From: "Michael Fuhr"<mike(at)fuhr(dot)org>
Sent: 21/08/05 23:53:50
To: "pgsql-hackers(at)postgresql(dot)org"<pgsql-hackers(at)postgresql(dot)org>
Subject: [HACKERS] Sleep functions
> What do people think of exposing
> pg_usleep() to the user?
Good idea - I've done so myself in the past for testing.
Regards, Dave
-----Unmodified Original Message-----
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.
--
Michael Fuhr
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
From | Date | Subject | |
---|---|---|---|
Next Message | Satoshi Nagayasu | 2005-08-22 00:01:13 | Pre-allocated free space for row updating (like PCTFREE) |
Previous Message | Andrew Dunstan | 2005-08-21 23:24:03 | Re: Sleep functions |