Re: doc: improve the restriction description of using indexes on REPLICA IDENTITY FULL table.
От | Amit Kapila |
---|---|
Тема | Re: doc: improve the restriction description of using indexes on REPLICA IDENTITY FULL table. |
Дата | |
Msg-id | CAA4eK1+EjuTfzD8vviXu1sxW=_gYsAMUSUhoTEaWJwJv082HYw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: doc: improve the restriction description of using indexes on REPLICA IDENTITY FULL table. (Masahiko Sawada <sawada.mshk@gmail.com>) |
Ответы |
Re: doc: improve the restriction description of using indexes on REPLICA IDENTITY FULL table.
Re: doc: improve the restriction description of using indexes on REPLICA IDENTITY FULL table. |
Список | pgsql-hackers |
On Wed, Jul 12, 2023 at 12:31 PM Masahiko Sawada <sawada.mshk@gmail.com> wrote: > > On Tue, Jul 11, 2023 at 5:31 PM Peter Smith <smithpb2250@gmail.com> wrote: > > > > I don't think we have concluded any action for it. I agree that > IsIndexOnlyOnExpression() is redundant. We don't need to check *all* > index fields actually. I've attached a draft patch. It removes > IsIndexOnlyOnExpression() and merges > RemoteRelContainsLeftMostColumnOnIdx() to > FindUsableIndexForReplicaIdentityFull. One concern is that we no > longer do the assertion check with > IsIndexUsableForReplicaIdentityFull(). What do you think? > I think this is a valid concern. Can't we move all the checks (including the remote attrs check) inside IsIndexUsableForReplicaIdentityFull() and then call it from both places? Won't we have attrmap information available in the callers of FindReplTupleInLocalRel() via ApplyExecutionData? -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: