On Tue, 13 Oct 2026 at 13:11, vignesh C <[email protected]> wrote: > > I think the same issue can occur in other callers of > InvalidatePublicationRels() apart from the reported adding tables in a > schema, such as altering publication options, dropping a table from a > publication, and dropping a schema from a publication. We can safely > ignore relations that have been dropped concurrently in these cases. > The other caller, which adds a table directly to a publication, is not > affected because it locks the table and prevents it from being dropped > concurrently. So, we can continue to throw an error if the table no > longer exists in that case.
The attached v2 version patch has the changes for the same. This also addresses hou-san comment of not requiring a new function from [1]. [1] - https://www.postgresql.org/message-id/CAFvd2n-rM%3DMdNjNq8VvSx_0rxWiDpmdXK31OAiSP%3DG0d6a29TQ%40mail.gmail.com Regards, Vignesh
v2-0001-Avoid-cache-lookup-failure-for-concurrently-dropp.patch
Description: Binary data
