GitHub user mg1986jp added a comment to the discussion: function
read_parquet(unknown) does not exist
The `read_parquet` function exists in DuckDB but not in PostgreSQL. When you
run queries through Superset's SQL Lab, it goes through the SQLAlchemy
connection, and if pgduckdb isn't properly loaded as an extension in that
connection, PostgreSQL's query planner doesn't know about DuckDB functions.
The issue is probably that pgduckdb loads as a session-level extension, and
each Superset SQL Lab query might use a different connection from the pool
where the extension isn't loaded.
Try adding this to your Superset database connection config — in the "Extra"
field of the database settings, you can set initialization commands:
```json
{
"engine_params": {
"connect_args": {
"options": "-c shared_preload_libraries=pg_duckdb"
}
}
}
```
Or run `LOAD 'pg_duckdb'` at the start of each SQL Lab query. If pgduckdb needs
to be loaded per-session, you might need to configure it as a
`shared_preload_library` in postgresql.conf so it's always available.
GitHub link:
https://github.com/apache/superset/discussions/40453#discussioncomment-17083280
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
