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 | CAA4eK1Jbdj--7zMdDJv=kZaCSQnFUjDC7BWpscmGYUj2F=3MdA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: doc: improve the restriction description of using indexes on REPLICA IDENTITY FULL table. (Masahiko Sawada <sawada.mshk@gmail.com>) |
Список | pgsql-hackers |
On Wed, Jul 5, 2023 at 12:02 PM Masahiko Sawada <sawada.mshk@gmail.com> wrote: > > On Wed, Jul 5, 2023 at 2:46 PM Amit Kapila <amit.kapila16@gmail.com> wrote: > > > > On Wed, Jul 5, 2023 at 9:01 AM Peter Smith <smithpb2250@gmail.com> wrote: > > > > > > Hi. Here are some review comments for this patch. > > > > > > +1 for the patch idea. > > > > > > ------ > > > > > > I wasn't sure about the code comment adjustments suggested by Amit [1]: > > > "Accordingly, the comments atop build_replindex_scan_key(), > > > FindUsableIndexForReplicaIdentityFull(), IsIndexOnlyOnExpression() > > > should also be adjusted." > > As for IsIndexOnlyOnExpression(), what part do you think we need to > adjust? It says: > > /* > * Returns true if the given index consists only of expressions such as: > * CREATE INDEX idx ON table(foo(col)); > * > * Returns false even if there is one column reference: > * CREATE INDEX idx ON table(foo(col), col_2); > */ > > and it seems to me that the function doesn't check if the leftmost > index column is a non-expression. > Right, so, we can leave this as is. -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: