From: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
---|---|
To: | Ivar <ivar(at)lumisoft(dot)ee> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Functions have 32 args limt ??? |
Date: | 2003-08-28 15:10:24 |
Message-ID: | 20030828080912.T6403-100000@megazone.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, 28 Aug 2003, Ivar wrote:
> I don't see why default is so small.
Re-read Joe's response. There are performance and disk usage tradeoffs
for raising the limit. I'd suggest looking at the mailing list archives
for the discussion mentioned.
> "Joe Conway" <mail(at)joeconway(dot)com> wrote in message
> news:3F4D8DE0(dot)1060307(at)joeconway(dot)com(dot)(dot)(dot)
> > Ivar wrote:
> > > For my supprise I found that functions have 32 parameter limit.
> > >
> > > Where to find more info about this limitation or similar limitations ?
> > >
> > > I need at least 50, 100 would be ok.
> >
> > See INDEX_MAX_KEYS defined in src/include/pg_config.h.in
> > (pg_config_manual.h in postgres 7.4). Change to 64 or whatever and
> > recompile. But note that you'll need to dump, initdb, and reload your
> > data. Also note that there are performance and disk usage tradeoffs --
> > search the mailing list archives from August 2002 for some test results
> > and discussion.
> >
> > Joe
> >
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 9: the planner will ignore your desire to choose an index scan if your
> > joining column's datatypes do not match
> >
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>
From | Date | Subject | |
---|---|---|---|
Next Message | Marie G. Tuite | 2003-08-28 15:18:56 | Re: before trigger problem |
Previous Message | Shridhar Daithankar | 2003-08-28 14:54:43 | Re: Problems with transactions and sequences |