| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | jd(at)commandprompt(dot)com, 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 19:29:55 |
| Message-ID: | 20100222192955.GI4629@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Merlin Moncure escribió:
> 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?
Divide and conquer?
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2010-02-22 19:34:03 | Re: Recent vendor SSL renegotiation patches break PostgreSQL |
| Previous Message | Alvaro Herrera | 2010-02-22 19:00:50 | Re: What does this configure warning mean? |