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-24 21:24:27 |
Message-ID: | CAB+=1TVAJTD=grwZ5RDQgpU2QzhkzqqkPwTJdbWW56ngkD+3dg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sun, 24 Mar 2024 at 20:29, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:
> On Sun, 2024-03-24 at 00:37 +0530, veem v wrote:
> > > Instead, use foreign keys between the partitions.
> >
> > I am struggling to understand how to maintain those partitions then?
> > As because we were planning to use pg_partman for creating and dropping
> > partitions automatically without much hassle.
>
> I understand.
>
> But do you want to pursue a way that is not working well, just because
> the tool you chose cannot handle it?
>
> Yours,
> Laurenz Albe
Thank you so much Laurenz.
Can you please suggest some docs which shows the way we should do the
partition maintenance (if not using pg_partman)?
Actually , I am not able to visualize the steps here. Do you mean to say ,
we will just create the partition tables without any foreign key
constraints first. Then create parent table future partitions first (say 10
days partitions) and then child table future 10 days partitions manually
and during that define the foreign key constraints , indexes etc. Here ,
how to exactly find the exact matching parent partitions so as to create
the foreign keys one to one?
From | Date | Subject | |
---|---|---|---|
Next Message | Thiemo Kellner | 2024-03-24 21:27:45 | Re: Empty materialized view |
Previous Message | Adrian Klaver | 2024-03-24 21:06:19 | Re: Empty materialized view |