Skip to content
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

Received unsupported data type Utf8 for BuiltIn(INT8OID) error when running EXPLAIN with ANALYZE option #1219

Closed
Mmoncadaisla opened this issue May 31, 2024 · 1 comment

Comments

@Mmoncadaisla
Copy link

Bug Description

When running a EXPLAIN ANALYZE command an error is returned:

ERROR:  Received unsupported data type Utf8 for BuiltIn(INT8OID). Please submit a request at https://github.com/paradedb/paradedb/issues if you believe this conversion should be supported

How To Reproduce

Environment settings:

  • Environment: Kubernetes (GKE) v1.27.12-gke.1115000
  • PostgreSQL version: PostgreSQL 16.3 (Debian 16.3-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
  • pg_lakehouse version: 0.7.3
  1. Create a foreign table (in my case a table that lives in Google Cloud Storage)
  2. Run a EXPLAIN command against a simple select count(*) from table - this works just fine
explain select count(*) from pglh_alos_dem_30m_h3_private;
                                      QUERY PLAN
--------------------------------------------------------------------------------------
 Aggregate  (cost=1.00..1.01 rows=1 width=8)
   ->  Foreign Scan on pglh_alos_dem_30m_h3_private  (cost=0.00..1.00 rows=1 width=0)
         Wrappers: quals = []
         Wrappers: tgts = []
         Wrappers: sorts = []
         Wrappers: limit = None
(6 rows)
  1. Run the same command but issue a EXPLAIN ANALYZE instead - this errors out.
explain analyze select count(*) from pglh_alos_dem_30m_h3_private;
ERROR:  Received unsupported data type Utf8 for BuiltIn(INT8OID). Please submit a request at https://github.com/paradedb/paradedb/issues if you believe this conversion should be supported
@Mmoncadaisla
Copy link
Author

I hadn't noticed this was already reported via #1152 (comment) closing this one...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant