From: | jian he <jian(dot)universality(at)gmail(dot)com> |
---|---|
To: | Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Fix tab completion in v18 for ALTER DATABASE/USER/ROLE ... RESET |
Date: | 2025-07-22 10:28:18 |
Message-ID: | CACJufxF5_23CykxYOFYeXMR6_XC+fjjUmY5NRf=JQDWR26q4XA@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jul 17, 2025 at 1:41 AM Dagfinn Ilmari Mannsåker
<ilmari(at)ilmari(dot)org> wrote:
>
> Hi hackers,
>
> These two patches are split out from my earlier thread about improving
> tab completion for varous RESET forms
> (https://postgr.es/m/87bjqwwtic.fsf@wibble.ilmari.org) so that the bug
> fixes can be tracked as an open item for v18.
>
> Commits 9df8727c5067 and c407d5426b87 added tab completion for ALTER
> DATABASE ... RESET and ALTER ROLE/USER ... RESET, respectively, but
> they're both differently buggy. The query for the DATABASE form
> neglected to schema-qualify the unnest() call, and the query for the
> ROLE/USER form shows all possible variables once you start typing a
> variable name, not just the ones that are set on the role. The attached
> patches fix both.
>
I played around with it, and overall it looks good.
From | Date | Subject | |
---|---|---|---|
Next Message | Arseniy Mukhin | 2025-07-22 10:47:18 | Re: amcheck: support for GiST |
Previous Message | shveta malik | 2025-07-22 10:27:34 | Re: Skipping schema changes in publication |