From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Question on pg_cron |
Date: | 2024-06-08 16:23:22 |
Message-ID: | CANzqJaD8iuULuUOUj9LXoGKBHAL1miSPsQ8jEV9UUYf3EDAaqw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sat, Jun 8, 2024 at 5:31 AM yudhi s <learnerdatabase99(at)gmail(dot)com> wrote:
> Hello All,
>
> We have around 10 different partition tables for which the partition
> maintenance is done using pg_partman extension. These tables have foreign
> key dependency between them. We just called partman.run_maintanance_proc()
> through pg_cron without any parameters and it was working fine. So we can
> see only one entry in the cron.job table. And it runs daily once.
>
> It was all working fine and we were seeing the historical partition being
> dropped and new partitions being created without any issue. But suddenly we
> started seeing, its getting failed with error "ERROR: can not drop
> schema1.tab1_part_p2023_12_01 because other objects depend on it"
>
Have you changed version lately of PG, pg_cron or pg_partman? Or maybe
what pg_cron or pg_partman depends on?
From | Date | Subject | |
---|---|---|---|
Next Message | yudhi s | 2024-06-08 16:34:48 | Re: Question on pg_cron |
Previous Message | Sushrut Shivaswamy | 2024-06-08 14:59:16 | Columnar Format Export in Postgres |