Re: [HACKERS] Changing oidvector length

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: [HACKERS] Changing oidvector length
Date: 2000-01-11 02:25:51
Message-ID: 14293.947557551@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2000-01-11 02:34:48 Re: [HACKERS] Changing oidvector length
Previous Message Hiroshi Inoue 2000-01-11 01:58:27 RE: [HACKERS] Potential vacuum bug?