Re: REINDEX backend filtering - Mailing list pgsql-hackers

From Zhihong Yu
Subject Re: REINDEX backend filtering
Date
Msg-id CALNJ-vS+gXt0OYBg671k9fVHWTUu+1cpNfoOA3PUsZKJp8Ey4w@mail.gmail.com
Whole thread Raw
In response to Re: REINDEX backend filtering  (Julien Rouhaud <rjuju123@gmail.com>)
List pgsql-hackers
Hi,
For index_has_deprecated_collation(),

+   object.objectSubId = 0;

The objectSubId field is not accessed by do_check_index_has_deprecated_collation(). Does it need to be assigned ?

For RelationGetIndexListFiltered(), it seems when (options & REINDEXOPT_COLL_NOT_CURRENT) == 0, the full_list would be returned.
This can be checked prior to entering the foreach loop.

Cheers

On Sat, Feb 6, 2021 at 11:20 PM Julien Rouhaud <rjuju123@gmail.com> wrote:
On Thu, Jan 21, 2021 at 11:12:56AM +0800, Julien Rouhaud wrote:
>
> There was a conflict with a3dc926009be8 (Refactor option handling of
> CLUSTER, REINDEX and VACUUM), so rebased version attached.  No other
> changes included yet.

New conflict, v3 attached.

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Prevent printing "next step instructions" in initdb and pg_upgrade
Next
From: "Joel Jacobson"
Date:
Subject: Re: jsonb_array_elements_recursive()