On a related note, you might be interested in
On Tue, Aug 23, 2005 at 09:42:27AM -0500, Don Drake wrote:
> Sorry for the delay in replying.
> The use-case that I have is the following. I'm writing a job-control
> tracking sub-system that will store when jobs are started, finished, failed,
> etc. I would like to have the ability to have a process that is requesting
> to start, to actually wait a specified period time before starting. It could
> wait for another job to finish. I'm writing this in plpgsql since I'm
> storing status in the db.
> On 8/22/05, Michael Fuhr <mike(at)fuhr(dot)org> wrote:
> > On Mon, Aug 22, 2005 at 08:34:29AM -0500, Don Drake wrote:
> > > I agree that a basic function (non-CPU intensive sleep) like this should
> > be
> > > built in.
> > It's being discussed in pgsql-hackers:
> > http://archives.postgresql.org/pgsql-hackers/2005-08/msg00633.php
> > Do you have any use cases in addition to what's already been
> > mentioned? Sleeping isn't really a database operation, so there
> > needs to be some justification for making it a standard function.
> > --
> > Michael Fuhr
> Donald Drake
> Drake Consulting
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com 512-569-9461
In response to
pgsql-admin by date
|Next:||From: Aldor||Date: 2005-08-23 19:39:34|
|Subject: Re: Fwd: Indexes (Disk space)|
|Previous:||From: Joshua D. Drake||Date: 2005-08-23 18:04:58|
|Subject: Re: EnterpriseDB ?|