Re: partitioned indexes and tablespaces
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>,
Michael Paquier <michael@paquier.xyz>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2018-11-02T15:57:47Z
Lists: pgsql-hackers
On Fri, Nov 2, 2018 at 11:02 AM Alvaro Herrera <alvherre@2ndquadrant.com> wrote: > > By the way, if we decide to do something about this, I think we do the > > same for partitioned tables. > > I'm up for changing the behavior of partitioned tables in pg12 (please > send a patch), but I'm up for changing the behavior of partitioned > tables in pg11. Uh, what? I strongly object to inserting behavior changes into released branches on the grounds that the behavior wasn't considered carefully enough before feature freeze. If we accept that as a justification, then anybody can claim that any behavior change should be back-patched at any time as long as they were the author of the original patch. But that's not a recipe for a stable product. There's got to be a point at which we say, yeah, you know, this is maybe not the perfect set of design decisions, but we're going to support the decisions we made for the next 5 years. And maybe we'll make better ones in the next release. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Commits
-
Fix tablespace handling for partitioned indexes
- 33e6c34c3267 11.1 landed
- dfa608141982 12.0 landed