public inbox for [email protected]
help / color / mirror / Atom feedFrom: Ron Johnson <[email protected]>
To: pgsql-general <[email protected]>
Subject: Re: Question on pg_cron
Date: Sat, 8 Jun 2024 12:23:22 -0400
Message-ID: <CANzqJaD8iuULuUOUj9LXoGKBHAL1miSPsQ8jEV9UUYf3EDAaqw@mail.gmail.com> (raw)
In-Reply-To: <CAEzWdqdHXZRpOq75Tkj-4JL1S_Q3vtL-9KJasubhhELAvapRuA@mail.gmail.com>
References: <CAEzWdqdHXZRpOq75Tkj-4JL1S_Q3vtL-9KJasubhhELAvapRuA@mail.gmail.com>
On Sat, Jun 8, 2024 at 5:31 AM yudhi s <[email protected]> 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?
view thread (3+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Question on pg_cron
In-Reply-To: <CANzqJaD8iuULuUOUj9LXoGKBHAL1miSPsQ8jEV9UUYf3EDAaqw@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox