Re: [PATCHES] [SQL] 16 parameter limit
От | Alvaro Herrera |
---|---|
Тема | Re: [PATCHES] [SQL] 16 parameter limit |
Дата | |
Msg-id | 20020415233404.57d7fc01.alvherre@atentus.com обсуждение исходный текст |
Ответ на | Re: [PATCHES] [SQL] 16 parameter limit ("Rod Taylor" <rbt@zort.ca>) |
Ответы |
Re: [PATCHES] [SQL] 16 parameter limit
Re: [PATCHES] [SQL] 16 parameter limit |
Список | pgsql-hackers |
En Mon, 15 Apr 2002 23:19:45 -0400 "Rod Taylor" <rbt@zort.ca> escribió: > On the note of NAMEDATALEN, a view in the INFORMATION_SCHEMA > definition is exactly 2 characters over the current limit. > > ADMINISTRABLE_ROLE_AUTHORIZATIONS > > Not that it's a great reason, but it isn't a bad one for increasing > the limit ;) http://archives.postgresql.org/pgsql-general/2002-01/msg00939.php (Tom Lane says both SQL92 and SQL99 specify 128 as the maximun identifier length) Anyway, how does one measure the perfomance impact of such a change? By merely changing the constant definition, or also by actually using long identifiers? I can do that if it's of any help, for various values perhaps. -- Alvaro Herrera (<alvherre[a]atentus.com>) "Las cosas son buenas o malas segun las hace nuestra opinion" (Lisias)
В списке pgsql-hackers по дате отправления: