On Tue, 2024-04-02 at 01:41 +0530, sud wrote: > On Thu, Mar 21, 2024 at 6:18 PM Laurenz Albe <laurenz.a...@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 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
