Skip site navigation (1) Skip section navigation (2)

Re: scheduler in core

From: Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>
To: Simon Riggs <simon(at)2ndquadrant(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>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: scheduler in core
Date: 2010-02-22 17:34:46
Message-ID: 3073cc9b1002220934i78de39e7iaa556969c8d4d5e1@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Sun, Feb 21, 2010 at 1:11 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
[...]
>> Dimitri Fontaine <dfontaine(at)hi-media(dot)com> writes:
>> > Dave Page <dpage(at)pgadmin(dot)org> writes:
>> >> Why not just use pgAgent? It's far more flexible than the design
>> >> you've suggested, and already exists.
>>
>> > What would it take to have it included in core,
>>
[...]
>
> 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...
so, is this idea (having some user processes be "tied" to postmaster
start/stop) going to somewhere?

it also could help if we you have processes LISTENing for NOTIFYs

-- 
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157

In response to

Responses

pgsql-hackers by date

Next:From: Joshua D. DrakeDate: 2010-02-22 17:35:29
Subject: Re: Recent vendor SSL renegotiation patches break PostgreSQL
Previous:From: Joshua D. DrakeDate: 2010-02-22 17:32:47
Subject: Re: Recent vendor SSL renegotiation patches break PostgreSQL

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group