Re: [PATCHES] [SQL] 16 parameter limit

From: Alvaro Herrera <alvherre(at)atentus(dot)com>
To: "Rod Taylor" <rbt(at)zort(dot)ca>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCHES] [SQL] 16 parameter limit
Date: 2002-04-16 03:34:04
Message-ID: 20020415233404.57d7fc01.alvherre@atentus.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches pgsql-sql

En Mon, 15 Apr 2002 23:19:45 -0400
"Rod Taylor" <rbt(at)zort(dot)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)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2002-04-16 03:34:06 Re: [SQL] 16 parameter limit
Previous Message Manuel Sugawara 2002-04-16 03:32:30 Re: regexp character class locale awareness patch

Browse pgsql-patches by date

  From Date Subject
Next Message Peter Eisentraut 2002-04-16 03:34:06 Re: [SQL] 16 parameter limit
Previous Message Josh Berkus 2002-04-16 03:25:20 Re: [SQL] 16 parameter limit

Browse pgsql-sql by date

  From Date Subject
Next Message Peter Eisentraut 2002-04-16 03:34:06 Re: [SQL] 16 parameter limit
Previous Message Josh Berkus 2002-04-16 03:25:20 Re: [SQL] 16 parameter limit