Re: [PATCH] Fix psql tab completion for REPACK boolean options

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
Cc: Baji Shaik <baji(dot)pgdev(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [PATCH] Fix psql tab completion for REPACK boolean options
Date: 2026-05-15 09:36:21
Message-ID: CAHGQGwGAY4kfDtC4i+hAOX-a3u0yOA6__6EDTQz-ytsDHgh-yQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, May 13, 2026 at 9:46 PM Álvaro Herrera <alvherre(at)kurilemu(dot)de> wrote:
> > Thanks for the patch! It looks good to me.
> > Unless there are objections, I will commit it.
>
> Yeah, looks good to me, thanks.

I've pushed the patch. Thanks!

> Fine with me. I wouldn't have a problem saying it's a backpatchable
> bugfix, but it's certainly not very high priority or criticality.

Agreed.

BTW, while testing REPACK boolean options, I found two other issues
in their parsing.

First, REPACK (CONCURRENTLY OFF) failed with:

ERROR: unrecognized REPACK option "concurrently"

even though REPACK (CONCURRENTLY ON) works correctly. That is,
CONCURRENTLY was treated as an unrecognized option when disabled.

Second, when the same option is specified multiple times, the last value
is not always honored. In particular, if any occurrence sets an option to ON,
the option remains enabled even when the final setting is OFF.

I think these are bugs, and the attached patch fixes them. Thoughts?

Regards,

--
Fujii Masao

Attachment Content-Type Size
v1-0001-Fix-parsing-of-REPACK-options.patch application/octet-stream 2.6 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Zsolt Parragi 2026-05-15 09:50:44 Re: Bug? pg_rewind produces unusable but starting database with standby recovery
Previous Message Chao Li 2026-05-15 09:31:55 doc: fix pg_restore_extended_stats() example syntax