Re: scheduler in core

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>
Cc: Simon Riggs <simon(at)2ndquadrant(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>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: scheduler in core
Date: 2010-02-22 18:18:03
Message-ID: 4B82CA5B.3060300@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jaime Casanova wrote:
> On Sun, Feb 21, 2010 at 1:11 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>> There is currently no way to run a separate daemon process that runs
>> user code as part of Postgres, so that the startup code gets run
>> immediately we startup, re-run if we crash and shut down cleanly when
>> the server does. If there were some way to run arbitrary code in a
>> daemon using an extensibility API then we wouldn't ever get any requests
>> for the scheduler, cos you could write it yourself without troubling
>> anybody here.
>
> ah! that could get rid of one of my complaints, and then i could just
> work the rest in pgAgent...

Yeah, seems like a good idea. Slon daemon and similar daemons could also
use it.

> so, is this idea (having some user processes be "tied" to postmaster
> start/stop) going to somewhere?

I've added this to the TODO list. Now we just need someone to write it.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2010-02-22 18:22:23 Re: scheduler in core
Previous Message Pavel Stehule 2010-02-22 18:16:57 Re: Reason why set-value functions not allowed in GREATEST(), etc?