Re: Is there a drawback when changing NAMEDATALEN to 64?

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Is there a drawback when changing NAMEDATALEN to 64?
Дата
Msg-id 29510.1010769119@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Is there a drawback when changing NAMEDATALEN to 64?  (Frank Joerdens <frank@joerdens.de>)
Ответы Re: Is there a drawback when changing NAMEDATALEN to 64?  (Bruce Momjian <pgman@candle.pha.pa.us>)
Список pgsql-general
Frank Joerdens <frank@joerdens.de> writes:
> Is there a drawback when changing NAMEDATALEN to 64? Put the other way
> 'round, what's the thinking behind having a default of 32?

That value was chosen years ago, when machines were slower and disks
smaller than today.

There's been a proposal on the table for awhile to increase the standard
NAMEDATALEN value to 64, but we haven't got round to it.

BTW, there is at least a small potential for breaking applications with
this change: NAMEDATALEN is part of the exported libpq ABI, because it
affects the representation of PGnotify structures.  When and if we do
change the standard setting, I'm inclined to reverse the order of the
fields in PGnotify, so that accesses to be_pid don't depend on
NAMEDATALEN.

            regards, tom lane

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

Предыдущее
От: Lenny Silver
Дата:
Сообщение: problem making postgresql
Следующее
От: Tom Lane
Дата:
Сообщение: Re: problem making postgresql