From: Tom Lane <tgl@sss.pgh.pa.us>
To: martin@arp242.net
cc: pgsql-docs@lists.postgresql.org
Subject: Re: Is it wise to include table inheritence in the tutorial?
In-reply-to: <156495686451.8638.382610819642178810@wrigleys.postgresql.org>
References: <156495686451.8638.382610819642178810@wrigleys.postgresql.org>
Comments: In-reply-to PG Doc comments form <noreply@postgresql.org>
	message dated "Sun, 04 Aug 2019 22:14:24 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <12461.1565014660.1@sss.pgh.pa.us>
Date: Mon, 05 Aug 2019 10:17:40 -0400
Message-ID: <12462.1565014660@sss.pgh.pa.us>
Precedence: bulk

PG Doc comments form <noreply@postgresql.org> writes:
> I was reading the tutorial here:
> https://www.postgresql.org/docs/11/tutorial-inheritance.html
> But on the "don't do this" Wiki, it is strongly advised not to use this:
> https://wiki.postgresql.org/wiki/Don't_Do_This#Don.27t_use_table_inheritance

That wiki entry is just some random person's opinion, it's not
project policy.

Having said that, the partitioning feature is approaching the
point of being mature enough to recommend to novices, so maybe
we should start thinking about adjusting the tutorial with that
in mind.  I wouldn't necessarily remove the inheritance section;
it's talking about OOP-style inheritance, which you can't get
with partitioning.

			regards, tom lane