Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails

Поиск
Список
Период
Сортировка
От Nathan Bossart
Тема Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
Дата
Msg-id Zz1bvchIEQPT6eTr@nathan
обсуждение исходный текст
Ответ на Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
Список pgsql-bugs
On Tue, Nov 19, 2024 at 06:09:44PM -0500, Tom Lane wrote:
> Also, we could bypass the multiple lookups unless both the
> NAMEDATALEN-1'th and NAMEDATALEN-2'th bytes are non-ASCII, which
> should be rare enough to make it not much of a performance issue.

I'm admittedly not an expert in the multi-byte code, but since there are
encodings like LATIN1 that use a byte per character, don't we need to do
multiple lookups any time the NAMEDATALEN-1'th byte is non-ASCII?

> One annoying point is that we also need this for role lookup.

Right.

-- 
nathan



В списке pgsql-bugs по дате отправления: