| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | jd(at)commandprompt(dot)com |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, Dave Page <dpage(at)pgadmin(dot)org>, Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: scheduler in core |
| Date: | 2010-02-22 18:42:43 |
| Message-ID: | b42b73151002221042m1759804m1317bc0f47e4b197@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Feb 20, 2010 at 8:06 PM, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
>
> That doesn't mean it isn't a really good idea. It would be nice to have
> a comprehensive job scheduling solution that allows me to continue
> abstract away from external solutions and operating system dependencies.
+1!
Aa scheduler is an extremely common thing to have to integrate with
the database. All of our commercial competitors have them, and they
are heavily used.
Like I noted above, what people want to schedule is going to be stored
procedures. Having both would virtually eliminate the need for
scripting outside the database, which is a pretty big deal since
external scripts are a real pain to keep cross platform. Since
there's probably a lot of overlapping problems in those two features,
why not tackle both at once?
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2010-02-22 18:49:29 | Re: Recent vendor SSL renegotiation patches break PostgreSQL |
| Previous Message | Jaime Casanova | 2010-02-22 18:34:16 | tie user processes to postmaster was:(Re: [HACKERS] scheduler in core) |