pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Achilleas Mantzios - cloud <a.mantzios@cloud.gatewaynet.com>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: PostgreSQL inheritance vs https://wiki.postgresql.org/wiki/Don%27t_Do_This
Date: Mon, 23 Oct 2023 10:35:43 -0400
Message-ID: <374847.1698071743@sss.pgh.pa.us> (raw)
In-Reply-To: <2f106761-daa8-6b26-013e-884da25322c2@cloud.gatewaynet.com>
References: <2f106761-daa8-6b26-013e-884da25322c2@cloud.gatewaynet.com>

Achilleas Mantzios - cloud <a.mantzios@cloud.gatewaynet.com> writes:
> someone added this section about inheritance :
>     Don't use table inheritance

That's one person's opinion.  (Well, they're not alone in it, but
it's just an opinion not a considered community position.)

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

There's zero chance we'd remove table inheritance.  In the first
place, we have too much concern for backwards compatibility, and
in the second place, table partitioning is built on top of it.
Probably no one is going to work hard on adding more features
directly concerned with non-partitioned inheritance, but it's
not going anywhere either.

You should certainly make the point that if your problem looks like
partitioning, you should use partitioning rather than some hand-rolled
use of plain inheritance.  But there are valid use-cases where you
actually do want more columns in the child tables than the parent.

			regards, tom lane





view thread (14+ messages)  latest in thread

Message-ID: <374847.1698071743@sss.pgh.pa.us>
Permalink:  ../374847.1698071743@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/374847.1698071743@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: tgl@sss.pgh.pa.us, a.mantzios@cloud.gatewaynet.com
  Subject: Re: PostgreSQL inheritance vs https://wiki.postgresql.org/wiki/Don%27t_Do_This
  In-Reply-To: <374847.1698071743@sss.pgh.pa.us>
  References: <2f106761-daa8-6b26-013e-884da25322c2@cloud.gatewaynet.com> <374847.1698071743@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox