On Tue, 16 Apr 2002 11:35:57 +0800
"Christopher Kings-Lynne" <chriskl@familyhealth.com.au> wrote:
> > > Are we staying at 16 as the default? I personally think we can
> > > increase it to 32 with little penalty,
> >
> > If you want to increase it, let's just increase it and not add any more
> > configure options. If someone wants more than 32 then we really need to
> > start talking about design issues.
>
> Why not give them the configure option? It's not good HCI to impose
> arbitrary limits on people...?
It's not an arbitrary limit -- users can easily change pg_config.h.
> We can default it to 32, since there's demand for it. If a particular user
> decided to configure it higher, then they do that knowing that it may cause
> performance degradation. It's good to give them that choice though.
What if someone actually uses functions with more than 32
arguments? Their code will not longer be portable among
PostgreSQL installations, and they'll need to get the local
admin to recompile.
I could see adding a configure option if there was a justifiable
reason for using functions with more than 32 arguments -- but
IMHO that is quite a bizarre situation anyway, as Peter said.
My vote is to set the default # of function args to some
reasonable default (32 sounds good), and leave it at that.
Cheers,
Neil
--
Neil Conway <neilconway@rogers.com>
PGP Key ID: DB3C29FC
