Re: Support tab completion for upper character inputs in psql - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Support tab completion for upper character inputs in psql
Date
Msg-id 24171b05-cf0f-3073-a73a-57b45b794049@enterprisedb.com
Whole thread Raw
In response to RE: Support tab completion for upper character inputs in psql  ("Tang, Haiying" <tanghy.fnst@cn.fujitsu.com>)
Responses RE: Support tab completion for upper character inputs in psql  ("tanghy.fnst@fujitsu.com" <tanghy.fnst@fujitsu.com>)
List pgsql-hackers
On 09.02.21 15:48, Tang, Haiying wrote:
> I'm still confused about the APPROPRIATE behavior of tab completion.
> It seems ALTER table/tablespace <name> SET/RESET is already case-insensitive.
> 
> For example
> # alter tablespace dbspace set(e[tab]
> # alter tablespace dbspace set(effective_io_concurrency
> 
> # alter tablespace dbspace set(E[tab]
> # alter tablespace dbspace set(EFFECTIVE_IO_CONCURRENCY

This case completes with a hardcoded list, which is done  
case-insensitively by default.  The cases that complete with a query  
result are not case insensitive right now.  This affects things like

UPDATE T<tab>

as well.  I think your first patch was basically right.  But we need to  
understand that this affects all completions with query results, not  
just the one you wanted to fix.  So you should analyze all the callers  
and explain why the proposed change is appropriate.



pgsql-hackers by date:

Previous
From: Alexey Lesovsky
Date:
Subject: Re: Asynchronous and "direct" IO support for PostgreSQL.
Next
From: Tom Lane
Date:
Subject: Re: logical replication worker accesses catalogs in error context callback