Reference-Partitioned Tables - Mailing list pgsql-general

Hi,

There is a proposal to include in future developments sectioning by reference, as in Oracle

https://docs.oracle.com/database/121/VLDBG/GUID-00923EB3-05F6-41F7-8437-E42FC9BD9571.htm#VLDBG1093

There is a widespread model when data related to properties of a superclass is stored in a base table, and data related to subclasses in a detail table. Or when the main entity has volatile additional parameters. A very simplified example in the attached image.

The most successful choice of partitioning table Contracts is sectioning by list with key column ContractTypeID. It would be nice if the table ContractDetails  is partitioned automatically like the parent table Contracts. Then we don't have to add a crutch column ContractTypeID to the table ContractDetails   and partition manually in sync with Contracts. This field also consumes disk space, since the table of details is usually large and there can be more than one partitioning key.

Thanks, best wishes.