RE: [PATCH] Improving index selection for logical replication apply with replica identity full - Mailing list pgsql-hackers

From Hayato Kuroda (Fujitsu)
Subject RE: [PATCH] Improving index selection for logical replication apply with replica identity full
Date
Msg-id OS9PR01MB12149AA0FBB1910556C840827F5EF2@OS9PR01MB12149.jpnprd01.prod.outlook.com
Whole thread
In response to Re: [PATCH] Improving index selection for logical replication apply with replica identity full  (Önder Kalacı <onderkalaci@gmail.com>)
List 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


pgsql-hackers by date:

Previous
From: Ashutosh Sharma
Date:
Subject: Re: Report bytes and transactions actually sent downtream
Next
From: Maxime Schoemans
Date:
Subject: Re: [PATCH] btree_gist: add cross-type integer operator support for GiST