From: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
---|---|
To: | Dave Page <dpage(at)pgadmin(dot)org> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: scheduler in core |
Date: | 2010-02-21 00:03:20 |
Message-ID: | 3073cc9b1002201603i2bb53987n96b4b26b8571b477@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Feb 20, 2010 at 4:37 PM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
> On Sat, Feb 20, 2010 at 9:33 PM, Jaime Casanova
> <jcasanov(at)systemguards(dot)com(dot)ec> wrote:
>> Hi,
>>
>> I'm trying to figure out how difficult is this
>
> Why not just use pgAgent? It's far more flexible than the design
> you've suggested, and already exists.
>
- it's not that easy if you don't have pgadmin
- i need to backup postgres database to backup the schedules
- the use pgagent here is not very extended but the few a know have
tried desisted because they
said: "not always executed the jobs"... i don't have any real evidence
of that and probably what happens
was that the pgagent daemon wasn't working (error prone), but being it
started by the postmaster get rid of that
problem...
The first one could be rid out with a set of functions in pgagent and
clear docs...
i can live with the other two at some degree... but getting rid of
the third one should be nice :)
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2010-02-21 00:08:32 | Re: alpha4 bundled -- please verify |
Previous Message | Josh Berkus | 2010-02-20 23:58:52 | Re: alpha4 bundled -- please verify |