IO Error: Unable to read binary COPY data from Postgres:

[vimota]

What happens?

Running a create table FROM postgres_scan on a table with tsvector/fts (but excluding the columns) fails with :

    internalBinding('errors').triggerUncaughtException(
                              ^

[Error: Invalid Error: IO Error: Unable to read binary COPY data from Postgres: ] {
  errno: -1,
  code: 'DUCKDB_NODEJS_ERROR'
}

To Reproduce

create table if not exists users as SELECT * exclude (fts) FROM postgres_scan('postgresql://<>:5432/postgres', 'public', 'users');

OS:

macOS 12.4

PostgreSQL Version:

PostgreSQL 14.1 on aarch64-unknown-linux-gnu, compiled by gcc (Ubuntu 10.3.0-1ubuntu1~20.04) 10.3.0, 64-bit

DuckDB Version:

0.7.0

DuckDB Client:

Nodejs

Full Name:

Victor Mota

Affiliation:

PinchedIO

Have you tried this on the latest master branch?

• I agree

Have you tried the steps to reproduce? Do they include all relevant data and configuration? Does the issue you report still appear there?

• I agree

[vimota]

Confirmed this happens even when I do a SELECT * (not using exclude (fts) ).

Could it be failing to parse some character? If it's helpful, this error doesn't happen for the same table without the fts/tsvector column.

[vimota]

hmm something weird is happening, I'm now seeing this error even when running the query on another postgres table that used to work fine (for many weeks on the older version as well as today on 0.7.0) but now fails every time.

[vimota]

Closed this as it looks like it was due to networking issues.