Re: [PATCH] Use indexes on the subscriber when REPLICA IDENTITY is full on the publisher
Önder Kalacı <onderkalaci@gmail.com>
From: Önder Kalacı <onderkalaci@gmail.com>
To: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>,
Amit Kapila <amit.kapila16@gmail.com>
Cc: "shiy.fnst@fujitsu.com" <shiy.fnst@fujitsu.com>, "wangw.fnst@fujitsu.com" <wangw.fnst@fujitsu.com>,
Marco Slot <marco.slot@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, Andres Freund <andres@anarazel.de>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-03-03T14:15:49Z
Lists: pgsql-hackers
Attachments
- v31_0001_use_index_on_subs_when_pub_rep_ident_full.patch (application/octet-stream) patch v31
Hi Hayato, Amit, all > > > ``` > + /* Build scankey for every non-expression attribute in the index. > */ > ``` > > I think that single line comments should not terminated by ".". > Hmm, looking into execReplication.c, many of the single line comments terminated by ".". Also, On the HEAD, the same comment has single line comment. So, I'd rather stick to that? > > ``` > + /* There should always be at least one attribute for the index > scan. */ > ``` > > Same as above. > Same as above :) > > > ``` > +#ifdef USE_ASSERT_CHECKING > + IndexInfo *indexInfo = BuildIndexInfo(idxrel); > + > + Assert(!IsIndexOnlyOnExpression(indexInfo)); > +#endif > ``` > > I may misunderstand, but the condition of usable index has alteady been > checked > when the oid was set but anyway the you confirmed the condition again > before > really using that, right? > So is it OK not to check another assumption that the index is b-tree, > non-partial, > and one column reference? IIUC we can do that by adding new function like > IsIndexUsableForReplicaIdentityFull() > that checks these condition, and then call at > RelationFindReplTupleByIndex() if > idxIsRelationIdentityOrPK is false. > I think adding a function like IsIndexUsableForReplicaIdentityFull is useful. I can use it inside FindUsableIndexForReplicaIdentityFull() and assert here. Also good for readability. So, I mainly moved this assert to a more generic place with a more generic check to RelationFindReplTupleByIndex > > 032_subscribe_use_index.pl > > ``` > +# Testcase start: SUBSCRIPTION CREATE/DROP INDEX WORKS WITHOUT ISSUES > ... > +# Testcase end: SUBSCRIPTION RE-CALCULATES INDEX AFTER CREATE/DROP INDEX > ``` > > There is still non-consistent case. > > Fixed, thanks Anyway, I see your point, so > if you want to keep the naming as you proposed at least don't change > the ordering for get_opclass_input_type() call because that looks odd > to me. (A small comment from Amit's previous e-mail) Sure, applied now. Attaching v31. Thanks for the reviews! Onder KALACI
Commits
-
Add the testcases for 89e46da5e5.
- 805b821e77a3 16.0 landed
-
Allow the use of indexes other than PK and REPLICA IDENTITY on the subscriber.
- 89e46da5e511 16.0 landed
-
Rework query relation permission checking
- a61b1f74823c 16.0 cited
-
Generalize ri_RootToPartitionMap to use for non-partition children
- fb958b5da86d 16.0 cited
-
Add wait_for_subscription_sync for TAP tests.
- 0c20dd33db16 16.0 cited
-
Logical replication
- 665d1fad99e7 10.0 cited