RE: [PATCH] Improving index selection for logical replication apply with replica identity full

From: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>
To: 'Önder Kalacı' <onderkalaci(at)gmail(dot)com>
Cc: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Ethan Mertz <ethan(dot)mertz(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Subject: RE: [PATCH] Improving index selection for logical replication apply with replica identity full
Date: 2026-06-22 12:10:59
Message-ID: OS9PR01MB12149AA0FBB1910556C840827F5EF2@OS9PR01MB12149.jpnprd01.prod.outlook.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dear Onder,

> Some history that may help, since the planner keeps coming up....

Thanks for the clarification. I cannot recall so detailed discussions.

> On the concern about scanning all indexes: I do not think it is a
> problem. We already walk the full index list today; this change only
> removes the early return. It runs only on first apply or after an
> invalidation, and the work is bounded by the number of indexes, which is
> small. A quick microbenchmark should confirm it is tiny next to the
> apply work itself.

Yes, I agreed it's not a serious problem. just I wanted to see such the micro
bench.

Best regards,
Hayato Kuroda
FUJITSU LIMITED

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Maxime Schoemans 2026-06-22 12:20:37 Re: [PATCH] btree_gist: add cross-type integer operator support for GiST
Previous Message Ashutosh Sharma 2026-06-22 11:54:30 Re: Report bytes and transactions actually sent downtream