From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Artur Litwinowicz <admin(at)ybka(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: elegant and effective way for running jobs inside a database |
Date: | 2012-03-07 21:10:56 |
Message-ID: | 19302.1331154656@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Merlin Moncure <mmoncure(at)gmail(dot)com> writes:
> sure, I get that, especially in regards to procedures. a server
> ticker though is a pretty small thing and it's fair to ask if maybe
> that should be exposed instead of (or perhaps in addition to) a job
> scheduling system.
I don't want to have a server-side ticker at all, especially not one
that exists only for a client that might or might not be there. We've
been doing what we can to reduce PG's idle-power consumption, which is
an important consideration for large-data-center applications. Adding a
new source of periodic wakeups is exactly the wrong direction to be
going.
There is no need for a ticker to drive a job system. It should be able
to respond to interrupts (if a NOTIFY comes in) and otherwise sleep
until the precalculated time that it next needs to launch a job.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Dan Ports | 2012-03-07 21:15:18 | Re: a slightly stale comment |
Previous Message | Tom Lane | 2012-03-07 21:03:21 | Re: NULL's support in SP-GiST |