Re: Selectively invalidate caches in pgoutput module - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Selectively invalidate caches in pgoutput module
Date
Msg-id CAA4eK1LmR_AiuYw=s3VsMpSjv19WnbqOLV7R6uGHz3NvwmXu5Q@mail.gmail.com
Whole thread Raw
In response to RE: Selectively invalidate caches in pgoutput module  ("Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>)
List pgsql-hackers
On Mon, Mar 10, 2025 at 6:42 PM Hayato Kuroda (Fujitsu)
<kuroda.hayato@fujitsu.com> wrote:
>
> > Currently, only the leaf partition is invalidated when the published table is
> > partitioned. However, I think pgoutput could cache both the partitioned table
> > and the leaf partition table as relsync entries.
> >
> > For INSERT/UPDATE/DELETE on a partitioned table, only the leaf partition's
> > relsync entry is used in pgoutput, but the TRUNCATE references the parent
> > table's relsync entry.
>
> I think your analysis is correct. PSA new version. Below part contains my analysis.
>

I have made several cosmetic changes atop 0001 patch in the attached.
Additionally, fixed an issue in AddRelsyncInvalidationMessage() to
consider invalidating all the RelSyncCache entries. Kindly include
these in the next version if you find the changes are okay.

--
With Regards,
Amit Kapila.

Attachment

pgsql-hackers by date:

Previous
From: Aleksander Alekseev
Date:
Subject: Re: [PATCH] Add reverse(bytea)
Next
From: Nisha Moond
Date:
Subject: Re: Conflict detection for multiple_unique_conflicts in logical replication