Re: hyrax vs. RelationBuildPartitionDesc

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>

To: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>

Cc: Robert Haas <robertmhaas@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, Alvaro Herrera <alvherre@2ndquadrant.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2019-04-10T11:09:22Z

Lists: pgsql-hackers

On Wed, Apr 10, 2019 at 05:03:21PM +0900, Amit Langote wrote:
> The problem lies in all branches that have partitioning, so it should be
> listed under Older Bugs, right?  You may have noticed that I posted
> patches for all branches down to 10.

I have noticed.  The message from Tom upthread outlined that an open
item should be added, but this is not one.  That's what I wanted to
emphasize.  Thanks for making it clearer.
--
Michael

Commits

Load relcache entries' partitioning data on-demand, not immediately.
- 5b9312378e2f 13.0 landed
Prevent memory leaks associated with relcache rd_partcheck structures.
- d4c50b4b1f86 10.8 landed
- 5f1433ac5e7f 12.0 landed
- 089e4d405d0f 11.3 landed
Don't copy PartitionBoundInfo in set_relation_partition_info.
- c8151e642368 12.0 landed
Further reduce memory footprint of CLOBBER_CACHE_ALWAYS testing.
- d3f48dfae42f 12.0 landed
Fix some oversights in commit 2455ab488.
- de570047993b 12.0 landed
Defend against leaks into RelationBuildPartitionDesc.
- 2455ab48844c 12.0 landed
Allow ATTACH PARTITION with only ShareUpdateExclusiveLock.
- 898e5e3290a7 12.0 cited