public inbox for [email protected]
help / color / mirror / Atom feedFrom: yudhi s <[email protected]>
To: Muhammad Ikram <[email protected]>
Cc: pgsql-general <[email protected]>
Subject: Re: Question on partman extension while relation exist
Date: Tue, 2 Jul 2024 13:24:07 +0530
Message-ID: <CAEzWdqdGyJKuKJYmvi8Xm0M9xKvffcHS9wO4kQyFCnwTZLyd1w@mail.gmail.com> (raw)
In-Reply-To: <CAGeimVrmuHGCpg85oZuF0Y0DFDngEeYuceH8d3+Oe=Bu9-TrKA@mail.gmail.com>
References: <CAEzWdqfUnGNn1jpgVFr9+xCr5A-Pp9KjdxY=vv8E8iqqQ9OuFw@mail.gmail.com>
<CAGeimVrmuHGCpg85oZuF0Y0DFDngEeYuceH8d3+Oe=Bu9-TrKA@mail.gmail.com>
On Tue, 2 Jul, 2024, 12:43 pm Muhammad Ikram, <[email protected]> wrote:
> Hi Yudhi,
>
> I think disabling foreign keys before maintenance will help.
>
> --
> Muhammad Ikram
>
Do you mean to say call the parent table first for maintenance followed by
child, and remove all the foreign key first which are pointing to this
parent table partition which is going to be dropped by the pg_partman?
As drop/create partition is being called from within pg_partman without our
intervention, so where should we put this drop foreign key code? Do you
mean having that with another event trigger which will fire before drop?
view thread (2+ messages)
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], [email protected]
Subject: Re: Question on partman extension while relation exist
In-Reply-To: <CAEzWdqdGyJKuKJYmvi8Xm0M9xKvffcHS9wO4kQyFCnwTZLyd1w@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