| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
| Cc: | "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com>, "ShlokKumar(dot)Kyal(at)fujitsu(dot)com" <ShlokKumar(dot)Kyal(at)fujitsu(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Selectively invalidate caches in pgoutput module |
| Date: | 2025-03-11 08:52:22 |
| Message-ID: | CAA4eK1LmR_AiuYw=s3VsMpSjv19WnbqOLV7R6uGHz3NvwmXu5Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Mar 10, 2025 at 6:42 PM Hayato Kuroda (Fujitsu)
<kuroda(dot)hayato(at)fujitsu(dot)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 | Content-Type | Size |
|---|---|---|
| v9_001_topup_amit.patch.txt | text/plain | 4.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nisha Moond | 2025-03-11 08:58:42 | Re: Conflict detection for multiple_unique_conflicts in logical replication |
| Previous Message | Aleksander Alekseev | 2025-03-11 08:29:15 | Re: [PATCH] Add reverse(bytea) |