-
Notifications
You must be signed in to change notification settings - Fork 53
Inconsistent results from querying postgres numeric columns #136
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
Comments
also, i'm still getting am using |
Thanks for the report! I've pushed a fix for the decimal issue in #138. I will have another look at the Aurora issue. |
Fix #136 - correctly deal with decimals that have many leading zeros
The aurora issue seems to be fixed for me, you should likely run force install postgres_scanner from 'http://nightly-extensions.duckdb.org';
|
testing right away :) |
now i'm getting
(but only if using postgres_scan, if i use attach it seems to work besides the integer overflow) |
Ah yes. In general we recommend moving over to the |
is the fix for |
The binaries are uploaded but the caches are likely not invalidated yet, so you would need to wait a bit (or build from source yourself) |
trying to do that :) |
@Mytherin just an update,
|
What happens?
While using duckdb to query postgres, we are getting inconsistent results.
To Reproduce
in postgres
reading the value with duckdb 0.9.2 or 0.9.3 nightly yields a
IO Error: Postgres scanner - out of buffer in ReadInteger
(i tested also with previous duckdb versions and i got inconsistent results, with 0.9.0 i got 0.67 with the wrong number of zeros)
OS:
Mac
PostgreSQL Version:
16.1, observed on 14.9 too
DuckDB Version:
0.9.3.dev42, different issues on previous versions
DuckDB Client:
Python
Full Name:
Paolo Quadri
Affiliation:
Remote.com
Have you tried this on the latest
main
branch?Have you tried the steps to reproduce? Do they include all relevant data and configuration? Does the issue you report still appear there?
The text was updated successfully, but these errors were encountered: