From: | veem v <veema0000(at)gmail(dot)com> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Not able to purge partition |
Date: | 2024-03-21 19:12:42 |
Message-ID: | CAB+=1TW+bnifVFMtC4u5Ok2sjyse54iDK242v47txf4gotU7nw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, 21 Mar 2024 at 23:39, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:
> On Thu, 2024-03-21 at 22:50 +0530, veem v wrote:
> > So when you mentioned "to create the foreign keys *not* between the
> > partitioned table but between the individual partitions" , can that
> > be done using the same "partman.create_parent" procedure and automated
> > cron job schedule or has to be done any other way manually ?
>
> I don't know the capabilities of partmen, but I would be surprised if
> it could automatically create foreign keys on the partitions.
>
>
Yes, the constraints on each of the child partitions and parent partitions
were getting created automatically. As I see from
information_schema.table_constraints, it shows one foreign key constraint
in each of the child partitions created through the partman procedure.
It works smoothly without any issue, until we noticed this issue while
trying to purge the partition from the parent table partition. But I
believe this extension is extensively used , so I'm just wondering if I am
missing something here with regards to foreign key creation using this
automated partition creation/partman extension functionality.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2024-03-21 19:42:14 | Re: Slow GRANT ROLE on PostgreSQL 16 with thousands of ROLEs |
Previous Message | walther | 2024-03-21 18:47:17 | Re: Slow GRANT ROLE on PostgreSQL 16 with thousands of ROLEs |