| From: | Don Drake <dondrake(at)gmail(dot)com> |
|---|---|
| To: | Michael Fuhr <mike(at)fuhr(dot)org> |
| Cc: | John DeSoi <desoi(at)pgedit(dot)com>, Guido Barosio <gbarosio(at)gmail(dot)com>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: sleep? |
| Date: | 2005-08-23 14:42:27 |
| Message-ID: | 6c21003b05082307427ea67279@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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.
-Don
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
President
Drake Consulting
http://www.drakeconsult.com/
http://www.MailLaunder.com/
http://www.mobilemeridian.com/
312-560-1574
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2005-08-23 15:07:40 | Re: sleep? |
| Previous Message | Tom Lane | 2005-08-23 14:20:00 | Re: encoding issue with postgres 8.0 |