Re: [PATCH] Use direct hash lookup in logicalrep_partmap_invalidate_cb() - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [PATCH] Use direct hash lookup in logicalrep_partmap_invalidate_cb()
Date
Msg-id amasDGQ1sQae-0lh@paquier.xyz
Whole thread
In response to Re: [PATCH] Use direct hash lookup in logicalrep_partmap_invalidate_cb()  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On Sat, Apr 18, 2026 at 06:35:54AM +0900, Michael Paquier wrote:
> At this stage of the release cycle (aka feature freeze is in effect as
> of v19), I'd recommend that you add this patch to the next commit
> fest, so as this could be considered for v20, whose development should
> begin next July.  See [1].
>
> [1]: https://commitfest.postgresql.org/59/

I had this one marked for some time, so I have looked at it again and
I think that you are right to rely on the fact that a partition OID
would match with a localreloid, saving from what could be an expensive
sequential scan on a hash table.  Applied on HEAD as 0962f9e34439.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Nico Williams
Date:
Subject: Re: document the dangers of granting TRIGGER or REFERENCES
Next
From: Richard Guo
Date:
Subject: Re: Fix missing FORMAT when deparsing JSON_ARRAY(query)