duckdb/duckdb-postgres

Postgres_scanner does not detect the correct number of dimensions of an array in postgresql

Closed this issue · 2 comments

HackettJP commented

What happens?

if the array in postgresql in TEXT / float / VARCHAR that has two or more dimensions duckdb will either respond with either

with '\0' on the first tuple response of the query , on the second tuple will core dump / seg fault or go into unstable condition depending on the number of nested arrays.

To Reproduce

any array within Postgresql with 2 or more dimensions will crash duckdb

OS:

ubuntu 22.04

PostgreSQL Version:

15.2 (Ubuntu 15.2-1.pgdg22.04+1)

DuckDB Version:

0.7.1

DuckDB Client:

CLI on unix or C++ lib.

Full Name:

James Hackett

Affiliation:

none

Have you tried this on the latest master branch?

  • I agree

Have you tried the steps to reproduce? Do they include all relevant data and configuration? Does the issue you report still appear there?

  • I agree
Mytherin commented

Thanks for the report! This should be fixed now in #111.