Re: Support tab completion for upper character inputs in psql

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: Support tab completion for upper character inputs in psql
Дата
Msg-id 24171b05-cf0f-3073-a73a-57b45b794049@enterprisedb.com
обсуждение исходный текст
Ответ на RE: Support tab completion for upper character inputs in psql  ("Tang, Haiying" <tanghy.fnst@cn.fujitsu.com>)
Ответы RE: Support tab completion for upper character inputs in psql  ("tanghy.fnst@fujitsu.com" <tanghy.fnst@fujitsu.com>)
Список 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 по дате отправления:

Предыдущее
От: Alexey Lesovsky
Дата:
Сообщение: Re: Asynchronous and "direct" IO support for PostgreSQL.
Следующее
От: Tom Lane
Дата:
Сообщение: Re: logical replication worker accesses catalogs in error context callback