Re: Fix tab completion in v18 for ALTER DATABASE/USER/ROLE ... RESET - Mailing list pgsql-hackers

From Dagfinn Ilmari Mannsåker
Subject Re: Fix tab completion in v18 for ALTER DATABASE/USER/ROLE ... RESET
Date
Msg-id 87v7n8h24y.fsf@wibble.ilmari.org
Whole thread Raw
In response to Re: Fix tab completion in v18 for ALTER DATABASE/USER/ROLE ... RESET  (Tomas Vondra <tomas@vondra.me>)
List pgsql-hackers
Tomas Vondra <tomas@vondra.me> writes:

> On 7/30/25 12:17, Dagfinn Ilmari Mannsåker wrote:
>> 
>> ...
>> 
>>> @@ -5015,7 +5021,8 @@ match_previous_words(int pattern_id,
>>>      /* Complete with a variable name */
>>>      else if (TailMatches("SET|RESET") &&
>>>               !TailMatches("UPDATE", MatchAny, "SET") &&
>>> -             !TailMatches("ALTER", "DATABASE", MatchAny, "RESET"))
>>> +             !TailMatches("ALTER", "DATABASE", MatchAny, "RESET") &&
>>> +             !TailMatches("ALTER", "USER|ROLE", MatchAny, "RESET"))
>>>          COMPLETE_WITH_QUERY_VERBATIM_PLUS(Query_for_list_of_set_vars,
>>>                                            "CONSTRAINTS",
>>>                                            "TRANSACTION",
>> 
>> Instead of adding another !TailMatches() call, why not just change
>> "DATABASE" to "DATABASE|ROLE|USER"?
>
> It seemed to me separate calls would be easier to understand, but I see
> combine it like this in many other places, so done that way ...
>
> Pushed.

Thanks!

> Thanks for the fixes!
>
> regards



pgsql-hackers by date:

Previous
From: Andrei Lepikhov
Date:
Subject: Re: MergeAppend could consider sorting cheapest child path
Next
From: Tom Lane
Date:
Subject: Re: Making type Datum be 8 bytes everywhere