From: | Christophe Pettus <xof(at)thebuild(dot)com> |
---|---|
To: | Achilleas Mantzios - cloud <a(dot)mantzios(at)cloud(dot)gatewaynet(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: PostgreSQL inheritance vs https://wiki.postgresql.org/wiki/Don%27t_Do_This |
Date: | 2023-10-23 14:07:19 |
Message-ID: | CC12F2CB-1AC7-4790-BBD1-C3B339C80716@thebuild.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> On Oct 23, 2023, at 04:45, Achilleas Mantzios - cloud <a(dot)mantzios(at)cloud(dot)gatewaynet(dot)com> wrote:
> I believe this text is false on too many accounts. So, what's the consensus about Inheritance in PostgreSQL, I am going to give a talk on it in November and I wouldn't like to advertise/promote/teach something that the community has decided to abandon or drop. Actually I proposed several topics and they chose this one (Inheritance).
Is the topic literally table inheritance, or really table partitioning? Often, people who are not deeply experienced with PostgreSQL will use the term "inheritance" to mean table partitioning, since before version 10, inheritance was the only mechanism for doing partitioning. If what they really mean is partitioning, then you should focus on declarative partitioning (the newer scheme introduced in version 10), and if you mention table inheritance at all, it should be just to mention it's an obsolete way of doing partitioning.
If they really did mean table inheritance, that's a pretty esoteric feature to focus on at this point. I strongly suspect they meant partitioning, and are using the term "inheritance" loosely.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2023-10-23 14:35:43 | Re: PostgreSQL inheritance vs https://wiki.postgresql.org/wiki/Don%27t_Do_This |
Previous Message | Alvaro Herrera | 2023-10-23 14:01:56 | Re: PostgreSQL inheritance vs https://wiki.postgresql.org/wiki/Don%27t_Do_This |