-
Notifications
You must be signed in to change notification settings - Fork 82
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
Server crashes when executing "SELECT approx_count_distinct(a), approx_count_distinct(b) FROM t;" #567
Labels
CRASH
Postgres crashes
Comments
Hi @saygoodbyye! Thanks for reporting. I will have a look at it asap. |
@Y--, by the way, I also get warnings when building
|
Merged
Thanks, PR here #608 |
Y--
added a commit
that referenced
this issue
Feb 17, 2025
Because this can conflict with DuckDB's `postgres` extension which check scanner by name eg. https://github.com/duckdb/duckdb-postgres/blob/8461ed8b6f726564934e9c831cdc88d431e3148f/src/storage/postgres_insert.cpp#L193-L195 When `postgres` extension was loaded, the optimizer would try to then [cast](https://github.com/duckdb/duckdb-postgres/blob/8461ed8b6f726564934e9c831cdc88d431e3148f/src/storage/postgres_optimizer.cpp#L23) our `BindData` as its own, creating obvious problems :-) Fixes #567 #547
Hi @saygoodbyye this should have been fixed now (at least I can't reproduce it on my end anymore :-) Would you mind giving it a try as well? Thanks! |
@Y-- , Thank you, going to try |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happens?
Server crashes when executing the script below
PostgreSQL build:
To Reproduce
Sometimes you need to reproduce this sql-scripts several time to reproduce segfault.
backtrace:
OS:
debian-12 x86_64
pg_duckdb Version (if built from source use commit hash):
769c256
Postgres Version (if built from source use commit hash):
REL_17_STABLE (f4af4515bb5f3591d49bc16b6cb8ddbf66f98374)
Hardware:
No response
Full Name:
Egor Chindyaskin
Affiliation:
Postgres Professional
What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.
I have tested with a source build
Did you include all relevant data sets for reproducing the issue?
Yes
Did you include all code required to reproduce the issue?
Did you include all relevant configuration (e.g., CPU architecture, Linux distribution) to reproduce the issue?
The text was updated successfully, but these errors were encountered: