Re: Support tab completion for upper character inputs in psql

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Cc: tanghy(dot)fnst(at)fujitsu(dot)com, smithpb2250(at)gmail(dot)com, peter(dot)eisentraut(at)enterprisedb(dot)com, david(dot)zhang(at)highgo(dot)ca, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Support tab completion for upper character inputs in psql
Date: 2021-04-23 03:17:19
Message-ID: 1280270.1619147839@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> writes:
> All usages of pg_string_tolower don't need a copy.
> So don't we change the function to in-place converter?

Doesn't seem like a good idea, because that locks us into an assumption
that the downcasing conversion doesn't change the string's physical
length. There are a lot of counterexamples to that :-(. I'm not sure
that we actually implement such cases correctly today, but let's not
build APIs that prevent it from being fixed.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro Horiguchi 2021-04-23 03:25:36 Re: Support tab completion for upper character inputs in psql
Previous Message Etsuro Fujita 2021-04-23 03:12:58 Re: Asynchronous Append on postgres_fdw nodes.