-
Notifications
You must be signed in to change notification settings - Fork 52
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
query execution slow, unable to enable extensions or query parquet #177
Comments
Pardon my brevity, I'm answering from my phone. Hopefully this is enough to get you started:
|
@wuputah maybe your postgres table had an unsupported datatype?
|
@wuputah thanks - install_extension returns false regardless of the extension I try to install:
Also, do you want me to do a PR to fix the readme? Was able to query parquet after adding the second AS (missed that in README and I've never needed it using httpfs) however GROUP BY year() fails still. Not sure if date functions are supported yet. @mike-luabase - the table in question contains only - uuid, numeric, character varying (255), timestamp w/o time zone. Lmk if you want my table def & query, or is the varchar the issue? |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
No change in query performance directly against tables (Postgres: 2.1s, pg_duckdb: 2.1s, Mac M1 DuckDB: 0.025s) which leads me to believe it's falling back to the pgsql engine. Also unable to query parquet files, enable extensions, etc:
Postgres 16.3 Citus Cluster (Stackgres Operator) 1 Coordinator, 1 Shard with replicas - running in an Azure AKS x64 node
Compiled from source using custom docker image for Stackgres' Ubuntu containers running patroni
(Stackgres uses an older kernel w/ glibc 2.28)
Build image w/ make output is available here: https://hub.docker.com/repository/docker/killinterpol/quackbuster/general.
Let me know if you need more info, if I can troubleshoot further, run any available tests or otherwise contribute...
The text was updated successfully, but these errors were encountered: