From: | "Josh Berkus" <josh(at)agliodbs(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, John Proctor <jproctor(at)prium(dot)net>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: [SQL] 16 parameter limit |
Date: | 2002-04-16 04:06:44 |
Message-ID: | web-1371993@davinci.ethosmedia.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches pgsql-sql |
Peter,
> 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.
Actually, many Oracle DBAs use functions/procedures with up to 300
parameters. If we want them to take PostgreSQL seriously as an
alternative to Oracle, we need to be able to accommodate that, at the
very least through an accessable configure-time option.
Also, this is a very frequent request on the SQL list. The fact that
currently the defualt is 16 and pg_config.h is not documented anywhere,
is rather unfriendly to developers who like to use their functions as
pseudo-middleware.
John, please speak up here so the core team knows this isn't "just me."
-Josh Berkus
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-04-16 04:13:31 | Re: [SQL] 16 parameter limit |
Previous Message | Gavin Sherry | 2002-04-16 03:58:57 | Re: Importing Large Amounts of Data |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-04-16 04:13:31 | Re: [SQL] 16 parameter limit |
Previous Message | Bruce Momjian | 2002-04-16 03:57:20 | Re: [SQL] 16 parameter limit |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-04-16 04:13:31 | Re: [SQL] 16 parameter limit |
Previous Message | Bruce Momjian | 2002-04-16 03:57:20 | Re: [SQL] 16 parameter limit |