You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
COPY (SELECT * FROM {POSTGRES_DB}.{POSTGRES_SCHEMA}.{table_name}) TO '{table_dump_file}' (FORMAT PARQUET, COMPRESSION ZSTD, ROW_GROUP_SIZE 100000);
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?
Yes, I have
Did you include all relevant configuration (e.g., CPU architecture, Python version, Linux distribution) to reproduce the issue?
Yes, I have
The text was updated successfully, but these errors were encountered:
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: