| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Gabi Draghici <gabi(dot)draghici(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: pgagent |
| Date: | 2020-11-05 21:34:43 |
| Message-ID: | e594b31f-3af4-cf9a-64e4-ddcb2c15b4b3@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 11/5/20 1:07 PM, Gabi Draghici wrote:
>
> Hi,
>
> I have installed postgresql 12 on sles 15 for some tests. Now I'm
> interested in some sort of scheduler and from what I've read so far,
> pgagent should do the job. So I've installed pgagent 4.0. I've added a
> job (which I can see in pgagent.pga_job) but everytime I ran it (from
> pgadmin) nothing happens ! When I start the pgagent I can see "...
> pgagent ... connection authorized" in the main log. What else should I
> check ?
pg_cron:
https://www.citusdata.com/blog/2020/10/31/evolving-pg-cron-together/
For pgagent what is the job doing and when? Could it be it hasn't run
because it has not reached it's scheduled time.
>
> Thanks,
> Gabi
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2020-11-06 00:38:32 | Re: PANIC: could not write to log file {} at offset {}, length {}: Invalid argument |
| Previous Message | Gabi Draghici | 2020-11-05 21:07:12 | pgagent |