Re: partitioned indexes and tablespaces
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>, Andres Freund <andres@anarazel.de>, Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2018-11-07T18:21:59Z
Lists: pgsql-hackers
On 2018-Nov-07, Robert Haas wrote: > On Wed, Nov 7, 2018 at 10:46 AM Alvaro Herrera <alvherre@2ndquadrant.com> wrote: > > I think 11.0 is ready for testing that a migration from a production > > running 10.x, but not for just blindly migrating. If you wanted to take > > such a leap of faith, surely you'd wait for 11.1 at the very least. > > I think that's an irresponsible attitude for a committer to take. In > practice, you are probably right, but we shouldn't treat our > supposedly-stable releases as if they don't really need to be kept > stable. I take back that part actually, in the sense that I certainly wouldn't push patches that I didn't think were good reasonable bugfixes the week before a release. But, again, I don't think I was changing any behavior that anybody was relying on. Had anybody tried this case, they would have immediately complained that it didn't work the way they would expect, like #14590. > But maybe you've adopted that policy already. You back-patched a > behavior change 2 days before a minor release when the vote was 2-3 > against the change. It was? This is my count: For: Alvaro, Andrew, Tom Against: Michael, Robert, Andres Also, I contested every point that was raised about this patch. I don't think there were any remaining technical objections. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Fix tablespace handling for partitioned indexes
- 33e6c34c3267 11.1 landed
- dfa608141982 12.0 landed