-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IO Error: buffer_ptr not set in CheckHeader #270
Comments
I get the same error using duckdb CLI v1.0.0 when reading from a Timescale hypertable. |
Here to report the same thing, also with a Timescale table. |
In my case the errors disappeared after setting sane values for PG config parameters:
So the errors might come from PG terminating the COPY connection when it is taking too long in respect to the above parameters. |
Thanks for reporting! I've managed to reproduce this issue by setting a low statement timeout and running a query that triggers a lot of work in the server: ATTACH 'dbname=postgresscanner options=''-c statement_timeout=10000''' AS s (TYPE POSTGRES, READ_ONLY);
SELECT * FROM postgres_query(s, 'select count(*) from tbl, tbl t2');
-- IO Error: buffer_ptr not set in CheckHeader As indicated this is not really a problem we can fix as it is a Postgres configuration problem - but I'll rework the error message to be more descriptive. |
…Data returns -1 (no error and no header/data)
Fix #270: print a more descriptive error message when PQgetCopyData returns -1 (no error and no header/data)
What happens?
Using DuckDB to export a PostgreSQL table to a Parquet file, if the table in PostgreSQL is a view, you may encounter the following error
IO Error: buffer_ptr not set in CheckHeader
. I haven't figured out the exact reason yet.To Reproduce
OS:
x86_64
DuckDB Version:
1.1.2
DuckDB Client:
Python
Hardware:
No response
Full Name:
Cobol
Affiliation:
Inventec
What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.
I have not tested with any build
Did you include all relevant data sets for reproducing the issue?
No - Other reason (please specify in the issue body)
Did you include all code required to reproduce the issue?
Did you include all relevant configuration (e.g., CPU architecture, Python version, Linux distribution) to reproduce the issue?
The text was updated successfully, but these errors were encountered: