Re: BUG #5748: Invalid oidvector data during binary recv

On 2010-11-11 17:56, Tom Lane wrote:
> Yeb Havinga<yebhavinga(at)gmail(dot)com> writes:
>> If there is going to be a patch fixing things, the value
>> '{"1"}'::oidvector[] can't be exported and imported through binary send
>> recv as well.
> That's pilot error, nothing more nor less. (oidvector != oidvector[])
We're not trying to import the '{"1"}' binary value with oidvectorrecv.
We hit the error in oidvectorrecv because we binary received an
oidvector[] (through array_recv), so made an initial test case with an
oidvector, not oidvector[].

Anyway I now have troubles to make a good test case to trip the lbound
check. The actual oidvector array that failed was '{"23 23 2275 2281
23","",2281,26,2275,23,"25 25",701,25,20,1700,"23 23","701
701",21,700,"1700 1700","603 603","2281 2281","20 20","600 600","718
718","21 21",1022,"2281 26 2281 23","2281 26 2281 21 2281","17 17","20
23",602,869,1186,"601"}', but when I test with that now, the non-zero
lbound value is on a oidvector that also has a zero ndim.

IOW: sorry for the noise, just trying to make a good bug report.

regards,
Yeb Havinga