Skip site navigation (1) Skip section navigation (2)

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

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Yeb Havinga <yebhavinga(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5748: Invalid oidvector data during binary recv
Date: 2010-11-11 15:36:22
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
On 11.11.2010 16:30, Yeb Havinga wrote:
> The following bug has been logged online:
> Bug reference:      5748
> Logged by:          Yeb Havinga
> Email address:      yebhavinga(at)gmail(dot)com
> PostgreSQL version: 9.0.1
> Operating system:   Linux
> Description:        Invalid oidvector data during binary recv
> Details:
> postgres=# create table a as select ''::oidvector;
> postgres=# copy a to '/tmp/test' with binary;
> COPY 1
> postgres=# copy a from '/tmp/test' with binary;
> ERROR:  invalid oidvector data
> The error caused by the ARR_LBOUND(result)[0] != 0) check in oidvectorrecv,
> and after some debugging and looking at common values of the lbound, I
> wonder if this check itself is correct.

That check was added a while ago to make it impossible to inject values 
into the system that the text input functions wouldn't accept. There is 
no way to create an oidvector with non-zero lower bound through 
oidvectorin. But it looks like the check is not right for an empty array.

Will fix, thanks for the report.

   Heikki Linnakangas

In response to

pgsql-bugs by date

Next:From: Tom LaneDate: 2010-11-11 15:48:10
Subject: Re: BUG #5748: Invalid oidvector data during binary recv
Previous:From: DenisDate: 2010-11-11 15:26:08
Subject: BUG #5749: Case sensivity of names of sequences.

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group