Re: hyrax vs. RelationBuildPartitionDesc

Amit Langote <amitlangote09@gmail.com>

From: Amit Langote <amitlangote09@gmail.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Andres Freund <andres@anarazel.de>, Alvaro Herrera <alvherre@2ndquadrant.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, amul sul <sulamul@gmail.com>
Date: 2019-06-07T04:02:56Z
Lists: pgsql-hackers
On Thu, Jun 6, 2019 at 3:47 PM Amit Langote <amitlangote09@gmail.com> wrote:
> While it's
> problematic that the session in which a new partition is attached to
> the parent relation broadcasts 2 SI messages to invalidate the parent
> relation [1], it's obviously better to fix how RelationClearRelation
> manipulates rd_pdoldcxt so that duplicate SI messages are not harmful,
> fixing the latter is hardly an option.

Sorry, I had meant to say "fixing the former/the other is hardly an option".

Thanks,
Amit



Commits

  1. Load relcache entries' partitioning data on-demand, not immediately.

  2. Prevent memory leaks associated with relcache rd_partcheck structures.

  3. Don't copy PartitionBoundInfo in set_relation_partition_info.

  4. Further reduce memory footprint of CLOBBER_CACHE_ALWAYS testing.

  5. Fix some oversights in commit 2455ab488.

  6. Defend against leaks into RelationBuildPartitionDesc.

  7. Allow ATTACH PARTITION with only ShareUpdateExclusiveLock.