Re: BUG #5748: Invalid oidvector data during binary recv - Mailing list pgsql-bugs

From Heikki Linnakangas
Subject Re: BUG #5748: Invalid oidvector data during binary recv
Date
Msg-id 4CDC1828.4080005@enterprisedb.com
Whole thread Raw
In response to Re: BUG #5748: Invalid oidvector data during binary recv  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #5748: Invalid oidvector data during binary recv  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On 11.11.2010 18:17, Tom Lane wrote:
> BTW ... it strikes me there's another inconsistency between oidvectorin
> and oidvectorrecv, namely that the former enforces a maximum of
> FUNC_MAX_ARGS elements whereas the latter has no such limit.

Yes, it does:

>         /* check length for consistency with oidvectorin() */
>         if (ARR_DIMS(result)[0] > FUNC_MAX_ARGS)
>                 ereport(ERROR,
>                                 (errcode(ERRCODE_INVALID_PARAMETER_VALUE),
>                                  errmsg("oidvector has too many elements")));
>

I suspect you're looking at an old version, that was added quite recently.

--
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com

pgsql-bugs by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Recovery bug
Next
From: Tom Lane
Date:
Subject: Re: BUG #5748: Invalid oidvector data during binary recv