| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Artur Litwinowicz <admin(at)ybka(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: elegant and effective way for running jobs inside a database |
| Date: | 2012-03-05 19:56:55 |
| Message-ID: | 1330977259-sup-581@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from Artur Litwinowicz's message of lun mar 05 16:18:56 -0300 2012:
> Dear Developers,
> I am looking for elegant and effective way for running jobs inside a
> database or cluster - for now I can not find that solution.
Yeah, it'd be good to have something. Many people say it's not
necessary, and probably some hackers would oppose it; but mainly I think
we just haven't agreed (or even discussed) what the design of such a
scheduler would look like. For example, do we want it to be able to
just connect and run queries and stuff, or do we want something more
elaborate able to start programs such as running pg_dump? What if the
program crashes -- should it cause the server to restart? And so on.
It's not a trivial problem.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2012-03-05 20:02:39 | Re: poll: CHECK TRIGGER? |
| Previous Message | Alvaro Herrera | 2012-03-05 19:53:37 | Re: foreign key locks, 2nd attempt |