Horton

Re: Declarative partitioning vs. sql_inheritance

Robert Haas <robertmhaas@gmail.com>

View thread View on postgr.es
From: Robert Haas <robertmhaas@gmail.com>
To: David Fetter <david@fetter.org>
Cc: Dmitry Ivanov <d.ivanov@postgrespro.ru>, Michael Paquier <michael.paquier@gmail.com>, Andres Freund <andres@anarazel.de>, Erik Rijkers <er@xs4all.nl>, Amit Langote <amitlangote09@gmail.com>, Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>, Rajkumar Raghuwanshi <rajkumar.raghuwanshi@enterprisedb.com>, Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>, Pg Hackers <pgsql-hackers@postgresql.org>, pgsql-hackers-owner@postgresql.org
Date: 2016-12-16T20:15:42Z
Lists: pgsql-hackers 
On Fri, Dec 16, 2016 at 2:34 PM, David Fetter <david@fetter.org> wrote:
> It occurs to me this probably isn't the only GUC that's basically just
> a foot gun at this point.
>
> Is 10 a good time to sweep and clear them?

We never make any progress trying to do these things "in bulk".  If
you think there are other GUCs that need to be removed, start a thread
for each one, or closely related group, and let's talk about it on the
merits.  On this thread, let's just decide whether or not to remove
sql_inheritance.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Commits

  1. Replace enum InhOption with simple boolean.

  2. Remove sql_inheritance GUC.