The following bug has been logged online:
Bug reference: 5748
Logged by: Yeb Havinga
Email address: yebhavi...@gmail.com
PostgreSQL version: 9.0.1
Operating system: Linux
Description:Invalid oidvector data during binary recv
Details:
postgres=# create table a as
On 2010-11-11 16:48, Tom Lane wrote:
"Yeb Havinga" writes:
postgres=# create table a as select ''::oidvector;
SELECT 1
postgres=# copy a to '/tmp/test' with binary;
COPY 1
postgres=# copy a from '/tmp/test' with binary;
ERROR: invalid oidvector data
On 2010-11-11 17:14, Heikki Linnakangas wrote:
On 11.11.2010 18:11, Yeb Havinga wrote:
We're currently reading data from a remote pg_statistics, in particular
stavalues1.. etc. Even when our own user defined relations do not make
use of oidvectors (or intvectors), during testing on arbi
On 2010-11-11 17:56, Tom Lane wrote:
Yeb Havinga 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 != oi
On 2010-11-11 17:02, Heikki Linnakangas wrote:
On 11.11.2010 17:48, Tom Lane wrote:
"Yeb Havinga" writes:
postgres=# create table a as select ''::oidvector;
SELECT 1
postgres=# copy a to '/tmp/test' with binary;
COPY 1
postgres=# copy a from '/tmp/test'
On 2010-11-15 11:40, Heikki Linnakangas wrote:
On 15.11.2010 12:08, Yeb Havinga wrote:
On 2010-11-11 17:02, Heikki Linnakangas wrote:
On 11.11.2010 17:48, Tom Lane wrote:
"Yeb Havinga" writes:
postgres=# create table a as select ''::oidvector;
SELECT 1
postgres=# copy a
