| From: | Neel Patel <neel(dot)patel(at)enterprisedb(dot)com> |
|---|---|
| To: | Mehmet Emin KARAKAŞ <emin100(at)gmail(dot)com>, Dave Page <dpage(at)pgadmin(dot)org>, Ashesh Vashi <ashesh(dot)vashi(at)enterprisedb(dot)com> |
| Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | Re: PgAgent leap year problem |
| Date: | 2020-03-04 05:23:36 |
| Message-ID: | CACCA4P2A=t9UcKYyiB3-Z0J3zNQNsa48UwWrwUJ90koTxNL99g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
Hi Mehmet,
It was a bug in pgAgent. Thank you for sharing the patch. I have reviewed
and tested, it is working fine.
Dave/Ashesh:- Can we commit this patch ?
Thanks,
Neel Patel
On Mon, Mar 2, 2020 at 5:26 PM Mehmet Emin KARAKAŞ <emin100(at)gmail(dot)com>
wrote:
> Hi,
>
> Scheduled tasks set as the last day of February this year did not work. In
> your schedule function have a small bug. Leap year function get year
> parameter, but your code is sending day as a parameter. Fixing patch
> attached in this mail.
>
> Best Regards...
>
> --
> MEHMET EMİN KARAKAŞ
> PostgreSQL DBA
>
> Turksat Satellite Communication and Cable TV Operations
> Konya Yolu 40. Km. 06839 Golbasi / ANKARA - TÜRKİYE
> Tel : +90 312 615 32 73
> Faks : +90 312 615 32 77
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashesh Vashi | 2020-03-04 06:52:46 | Re: PgAgent leap year problem |
| Previous Message | Akshay Joshi | 2020-03-02 13:25:49 | pgAdmin4 v4.19 candidate builds |