Ducklake fails to attach on 1.3.2 with the recent postgres nightly extension

[prakashbalaji]

What happens?

The same attach command works against duckdb 1.3.2 with the default postgres.

If we update the postgres from core_nightly the command fails to attach with the error below.

 port 5432 failed: FATAL:  no PostgreSQL user name specified in startup packet

To Reproduce

RDS postgres + S3 bucket.

duckdb 1.3.2
force install postgres from core_nightly
ATTACH IF NOT EXISTS 'ducklake:postgres:<RDS_POSTGRES>' AS tracer_bullet_ducklake (DATA_PATH 's3://<S3_BUCKET>');

OS:

macos

PostgreSQL Version:

16.2

DuckDB Version:

1.3.2

DuckDB Client:

ducdkb

Full Name:

Prakash

Affiliation:

Summation

Have you tried this on the latest main 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]

Thanks for the report! Can you connect to the Postgres instance normally, or does this only happen if you connect using DuckLake?

[prakashbalaji]

I just changed the FORCE INSTALL postgres from core_nightly to INSTALL postgres and we are able to see things work normally with both connectivity to ducklake and UI which shows data from ducklake all loading fine.

[Mytherin]

Understood - but does ATTACH 'postgres:....' directly without DuckLake being involved work, or does that also not work?

[prakashbalaji]

Just to cross check, I connected to postgres with the same credentials from TablePlus and connected fine.

[Mytherin]

Thanks - I managed to reproduce the issue using an RDS instance. I will investigate.

[prakashbalaji]

Without ducklake involved getting the same error.

port 5432 failed: FATAL:  no PostgreSQL user name specified in startup packet

[Mytherin]

I think we're running into a bug in Postgres itself here - bumping the Postgres to a more recent version seems to fix the issue from my side - #351

[prakashbalaji]

@Mytherin - We are probably on a even more recent version of postgres at 16.8 and still see the issue.

[Mytherin]

I meant the version of the Postgres client driver that is bundled into the extension, not the server version.