| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Yeb Havinga <yebhavinga(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #5748: Invalid oidvector data during binary recv |
| Date: | 2010-11-11 16:22:00 |
| Message-ID: | 4CDC1828.4080005@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-11-11 16:26:32 | Re: BUG #5748: Invalid oidvector data during binary recv |
| Previous Message | Heikki Linnakangas | 2010-11-11 16:20:20 | Re: Recovery bug |