Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r0c63-006nJE-5x for pgsql-general@arkaria.postgresql.org; Wed, 08 Nov 2023 06:31:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1r0c61-00Gvp3-IE for pgsql-general@arkaria.postgresql.org; Wed, 08 Nov 2023 06:31:25 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r0c60-00Gvou-Oy for pgsql-general@lists.postgresql.org; Wed, 08 Nov 2023 06:31:24 +0000 Received: from cloud.gatewaynet.com ([185.90.37.94]) by makus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r0c5w-004WAo-UF for pgsql-general@lists.postgresql.org; Wed, 08 Nov 2023 06:31:23 +0000 Content-Type: multipart/alternative; boundary="------------W9NRmJMnDQF7ktJae3etMaC3" Message-ID: <41913c85-9d05-4ac3-8159-8b4e5968b759@cloud.gatewaynet.com> Date: Wed, 8 Nov 2023 08:31:17 +0200 MIME-Version: 1.0 Subject: Re: PostgreSQL inheritance vs https://wiki.postgresql.org/wiki/Don%27t_Do_This Content-Language: en-US To: pgsql-general@lists.postgresql.org References: <2f106761-daa8-6b26-013e-884da25322c2@cloud.gatewaynet.com> From: Achilleas Mantzios In-Reply-To: <2f106761-daa8-6b26-013e-884da25322c2@cloud.gatewaynet.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------W9NRmJMnDQF7ktJae3etMaC3 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hello All Here is the presentation, it was done under "Percona University Athens". It went ok, I think, although people didn't seem to understand much, as the audience was MySQL/PostgreSQL/Mongo/Oracle mix. However some young people seemed to be interested as they asked questions afterwards. https://docs.google.com/presentation/d/15LmNmjSMAXzHDSlm0MgvHuhSPnmVijsytdPJOz3l13g/edit?usp=sharing It was an interesting event, I had the chance to speak to top MySQL hackers (including the founders of Percona, TiDB, FerretDB). The event was relatively friendly to PostgreSQL as well, I have to say. PostgreSQL was presented as catching up MySQL in terms of usage/growth. In some future similar events I'd love to prepare a better and more current presentation for the local Greek community! Στις 23/10/23 14:45, ο/η Achilleas Mantzios - cloud έγραψε: > > Hello All > > in the wiki above and specifically in this commit : > > https://wiki.postgresql.org/index.php?title=Don%27t_Do_This&type=revision&diff=33210&oldid=33082 > > someone added this section about inheritance : > > " > > > Don't use table inheritance > > Don't use table inheritance > . > If you think you want to, use foreign keys instead. > > > Why not? > > Table inheritance was a part of a fad wherein the database was closely > coupled to object-oriented code. It turned out that coupling things > that closely didn't actually produce the desired results. > > > When should you? > > Never …almost. Now that table partitioning is done natively, that > common use case for table inheritance has been replaced by a native > feature that handles tuple routing, etc., without bespoke code. > > One of the very few exceptions would be temporal_tables > extension if you are in > a pinch and want to use that for row versioning in place of a lacking > SQL 2011 support. Table inheritance will provide a small shortcut > instead of using |UNION ALL| to get both historical as well as current > rows. Even then you ought to be wary of caveats > > while working with parent table. > > " > > > 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). > -- Achilleas Mantzios IT DEV - HEAD IT DEPT Dynacom Tankers Mgmt --------------W9NRmJMnDQF7ktJae3etMaC3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
Hello All

Here is the presentation, it was done under "Percona University Athens". It went ok, I think, although people didn't seem to understand much, as the audience was MySQL/PostgreSQL/Mongo/Oracle mix. However some young people seemed to be interested as they asked questions afterwards.


It was an interesting event, I had the chance to speak to top MySQL hackers (including the founders of Percona, TiDB, FerretDB). The event was relatively friendly to PostgreSQL as well, I have to say. PostgreSQL was presented as catching up MySQL in terms of usage/growth.

In some future similar events I'd love to prepare a better and more current presentation for the local Greek community!

Στις 23/10/23 14:45, ο/η Achilleas Mantzios - cloud έγραψε:

Hello All

in the wiki above and specifically in this commit :

https://wiki.postgresql.org/index.php?title=Don%27t_Do_This&type=revision&diff=33210&oldid=33082

someone added this section about inheritance :

"

Don't use table inheritance

Don't use table inheritance. If you think you want to, use foreign keys instead.

Why not?

Table inheritance was a part of a fad wherein the database was closely coupled to object-oriented code. It turned out that coupling things that closely didn't actually produce the desired results.

When should you?

Never …almost. Now that table partitioning is done natively, that common use case for table inheritance has been replaced by a native feature that handles tuple routing, etc., without bespoke code.

One of the very few exceptions would be temporal_tables extension if you are in a pinch and want to use that for row versioning in place of a lacking SQL 2011 support. Table inheritance will provide a small shortcut instead of using UNION ALL to get both historical as well as current rows. Even then you ought to be wary of caveats while working with parent table.

"


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).

-- 
Achilleas Mantzios
 IT DEV - HEAD
 IT DEPT
 Dynacom Tankers Mgmt
--------------W9NRmJMnDQF7ktJae3etMaC3--