Received: from candle.pha.pa.us (216-55-132-35.dsl.san-diego.abac.net [216.55.132.35]) by postgresql.org (Postfix) with ESMTP id 68473474E42 for ; Mon, 15 Apr 2002 23:44:24 -0400 (EDT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.10.1) id g3G3iGg04889; Mon, 15 Apr 2002 23:44:16 -0400 (EDT) From: Bruce Momjian Message-Id: <200204160344.g3G3iGg04889@candle.pha.pa.us> Subject: Re: [PATCHES] [SQL] 16 parameter limit In-Reply-To: <20020415233404.57d7fc01.alvherre@atentus.com> To: Alvaro Herrera Date: Mon, 15 Apr 2002 23:44:16 -0400 (EDT) Cc: Rod Taylor , pgsql-hackers@postgresql.org X-Mailer: ELM [version 2.4ME+ PL97 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200204/769 X-Sequence-Number: 21433 Alvaro Herrera wrote: > (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. I think I would measure disk size change in a newly created database, and run regression for various values. That uses a lot of identifier lookups. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026