Re: Not able to purge partition

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: sud <suds1434(at)gmail(dot)com>
Cc: veem v <veema0000(at)gmail(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Not able to purge partition
Date: 2024-04-02 08:16:00
Message-ID: deb7131b6ef0672a93062bcd19026d9c95380953.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, 2024-04-02 at 01:41 +0530, sud wrote:
> On Thu, Mar 21, 2024 at 6:18 PM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:
> > > [create some partitions, then drop a partition of the referenced table]
> > >
> > > SQL Error [P0001]: ERROR: cannot drop table schema1.test_part_drop_parent_p2024_02_01 because other objects depend on it
> > > CONTEXT: SQL statement "DROP TABLE schema1.test_part_drop_parent_p2024_02_01"
>
> However, out of curiosity, does this default foreign key setup i.e. foreign keys
> between the table (but not between the partitions) also make the data load into
> the child partitions slower ( as it must be then looking and validating the presence
> of the keys across all the partitions of the parent table)?

The query checking the foreign key consistency should be somewhat more expensive,
since it has to undergo partition pruning to figure out which partition to query.

Yours,
Laurenz Albe

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Saksham Joshi 2024-04-02 08:58:52 Getting wrong datetime in database using insert into table query.
Previous Message Laurenz Albe 2024-04-02 08:08:44 Re: Timestamp conversion Error in dynamic sql script