From: | "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Joe Conway <mail(at)joeconway(dot)com>, Thomas Lockhart <lockhart(at)fourpalms(dot)org>, Neil Conway <nconway(at)klamath(dot)dyndns(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: FUNC_MAX_ARGS benchmarks |
Date: | 2002-08-06 09:47:21 |
Message-ID: | Pine.LNX.4.21.0208061044170.3235-100000@ponder.fairway2k.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 6 Aug 2002, Bruce Momjian wrote:
>
> As long as we allocate the full length for the funcarg and name types,
> we are going to have performance/space issues with increasing them,
> especially since we are looking at doubling or quadrupling those values.
>
> [snip]
>
> I think funcargs of 32 and name of 64 is the way to go for 7.3. If we
> find we need longer names or we find we can make them variable length,
> we can revisit the issue. However, variable length has a performance
> cost as well, so it is not certain we will ever make them variable
> length.
I was thinking of looking at turning names to varchars/text in order to test
the performance hit [in the first instance]. However doing a
find . -name \*\.\[ch\] | xargs grep NAMEDATALEN | wc -l
gives 185 hits and some of those are setting other macros. It seems to me there
is a fair amount of work involved in just getting variable length names into
the system so that they can be tested.
--
Nigel J. Andrews
Director
---
Logictree Systems Limited
Computer Consultants
From | Date | Subject | |
---|---|---|---|
Next Message | Gavin Sherry | 2002-08-06 12:18:00 | Better handling of parse errors |
Previous Message | Nigel J. Andrews | 2002-08-06 09:26:52 | Re: Proposal for psql wildcarding behavior w/schemas |