Michael Adler wrote: > On Sun, Aug 21, 2005 at 09:13:20PM -0400, Tom Lane wrote: > > Michael Fuhr <[EMAIL PROTECTED]> writes: > > > What do people think of exposing pg_usleep() to the user? > > > > I'm not real enthused about it. Generally speaking, a sleep() on the > > database side means you are idling while holding locks, and that does > > not seem like something we want to encourage people to do. > > > > As other responders noted, it's trivial to program this in any of the > > untrusted PL languages, So what you're really proposing is that we give > > sleep() to non-superusers, and that seems like a bit of a hard sell. > > Let's see a use-case or three. > > There may be a better alternative, but wouldn't this let application > writers easily test the effects of a long running transaction?
What is wrong with giving non-super-users sleep() access? It is a natural part of almost every programming language. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org
