Re: Refactor ReindexStmt and its "concurrent" boolean

On Wed, Sep 2, 2020 at 1:03 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> Hi all,
>
> $subject has been mentioned a couple of times, including today:
> https://www.postgresql.org/message-id/20200902010012.GE1489@paquier.xyz
>
> We have a boolean argument in ReindexStmt to control a concurrent
> run, and we also have in parallel of that a bitmask to control the
> options of the statement, which feels like a duplicate. Attached is a
> patch to refactor the whole, adding CONCURRENTLY as a member of the
> available options. This simplifies a bit the code.
>
> Any thoughts?

+1

struct ReindexIndexCallbackState
{
- bool concurrent; /* flag from statement */
+ bool options; /* flag from statement */
Oid locked_table_oid; /* tracks previously locked table */
};

Shouldn't options be an int? The rest of the patch looks good to me.