| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | 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:26:32 |
| Message-ID: | 16086.1289492792@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
> 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:
Oh, never mind ...
> I suspect you're looking at an old version, that was added quite recently.
No, just failing to scroll down far enough :-(. Better go find some
more caffeine.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yeb Havinga | 2010-11-11 16:51:40 | Re: BUG #5748: Invalid oidvector data during binary recv |
| Previous Message | Heikki Linnakangas | 2010-11-11 16:22:00 | Re: BUG #5748: Invalid oidvector data during binary recv |