Re: [HACKERS] Proposal: Local indexes for partitioned table
Simon Riggs <simon@2ndquadrant.com>
From: Simon Riggs <simon@2ndquadrant.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>,
Pg Hackers <pgsql-hackers@postgresql.org>, Maksim Milyutin <milyutinma@gmail.com>
Date: 2017-11-14T18:43:36Z
Lists: pgsql-hackers
On 14 November 2017 at 13:12, Robert Haas <robertmhaas@gmail.com> wrote: > On Tue, Nov 14, 2017 at 12:49 PM, Alvaro Herrera > <alvherre@alvh.no-ip.org> wrote: >> Here's the remaining bits, rebased. > > It's true that Tom and I reviewed patch 0001, as your proposed commit > message states. But it's also true that we both said that it probably > wasn't a good idea. I don't see any comments from you or Tom about patch 0001, which was simple refactoring and not much to complain about. Perhaps there is some confusion about the numbering? I see that Alvaro had taken your comments on memory contexts into account in his later patch. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Local partitioned indexes
- 8b08f7d4820f 11.0 landed
-
Fix StoreCatalogInheritance1 to use 32bit inhseqno
- 1ef61ddce908 11.0 landed
- 9a215fb4b5ec 9.3.21 landed
- 8a71ee628854 9.6.7 landed
- 61f08c016322 10.2 landed
- 1284d18b5de9 9.4.16 landed
- 0d993709a773 9.5.11 landed
-
Get rid of copy_partition_key
- 8a0596cb656e 11.0 landed
-
Simplify index_[constraint_]create API
- a61f5ab98638 11.0 landed