Re: [HACKERS] Changing oidvector length - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] Changing oidvector length
Date
Msg-id 14293.947557551@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Changing oidvector length  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: [HACKERS] Changing oidvector length
List pgsql-hackers
Bruce Momjian <pgman@candle.pha.pa.us> writes:
>> You may have gotten confused because fmgr.c allowed 9 args to be passed,
>> even though there's no way to declare such a function; I think this was
>> a hack to support some special system usage --- possibly selectivity
>
> btbuild, I believe.

Ah, you are right (it just blew up on me when I tried it at eight ;-)).

>> But if we are going to
>> increase the default MAX_ARGS above 8 then the issue goes away anyway,
>> and there's no need for fmgr.c to support more args than can normally
>> be declared.

This still holds though --- we will just require INDEX_MAX_ARGS to be
at least 9 from here on out...
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Hiroshi Inoue"
Date:
Subject: RE: [HACKERS] Potential vacuum bug?
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Changing oidvector length