On 10/24/24 21:58, David G. Johnston
wrote:
On Thursday, October 24, 2024, <thiemo@xxxxxxxxxxxxxxxxxxxx> wrote:
Up to version 17, partitioning of tables inheriting from other tables is not possible.
psql:../code_files/data_storage/PostgreSQL/tables/TOPO_ FILES.pg_sql:68: ERROR: no se puede crear una tabla particionada como hija de herencia
Hi, opinions vary, IMHO inheritance it is a nice feature to have especially in multi-tenant situation where tenants represent a division or subsidiary rather than a completely foreign entity which should live in total isolation, plus the ability to have data on the top owning or managing organization. IMHO nothing beats inheritance in fitting to the above model. Partitioning comes close but partitioned tables cannot have any data on their own. There are workarounds of course to that, but they don't fit like a glove. But again I have not tested in heavy xactional envs TBT, I am just saying the feature is handy for many applications and models. I use it personally in my company and love it. Could I do without it? of course, but it would be ugly.
Are there plans to support this in the future? I could not find any hint in the documentation or in https://wiki.postgresql.org/wiki/Development_information .
My impression of things is that directly using “inherit” for table creation is considered deprecated at this point. No one has interest in expanding on the feature nor even recommends it be used in new development. That particular unique feature of PostgreSQL hasn’t caught on.
David J.
