Re: Not able to purge partition - Mailing list pgsql-general

From Laurenz Albe
Subject Re: Not able to purge partition
Date
Msg-id deb7131b6ef0672a93062bcd19026d9c95380953.camel@cybertec.at
Whole thread Raw
In response to Re: Not able to purge partition  (sud <suds1434@gmail.com>)
List 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.albe@cybertec.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
dependon 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



pgsql-general by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: Timestamp conversion Error in dynamic sql script
Next
From: Saksham Joshi
Date:
Subject: [MASSMAIL]Getting wrong datetime in database using insert into table query.