Unrecognized option for Postgres attach: read_write

[steven-luabase]

What happens?

I'm hitting an error when trying to run an ATTACH statement to attach a Ducklake postgres catalog. Here is my attach statement:

attach 'ducklake:postgres:postgresql://postgres:password@host:5432/ducklake_catalog' as my_ducklake (DATA_PATH 'file_path');

It's throwing this error:

Unrecognized option for Postgres attach: read_write

However if I add READ_ONLY to the options like this:

attach 'ducklake:postgres:postgresql://postgres:password@host:5432/ducklake_catalog' as my_ducklake (DATA_PATH 'file_path', READ_ONLY);

It works.

The other thing to point out is that depending on the environment I'm in, it works/fails. For example if I'm running this in linux_amd64 platform I hit the error whereas if I run it in osx_arm64 platform it works. Both platforms have the same postgres extension version:

┌──────────────────┬─────────┬───────────┬──────────────────────┬────────────────────────────────────────────────────┬────────────┬───────────────────┬──────────────┬────────────────┐
│  extension_name  │ loaded  │ installed │     install_path     │                    description                     │  aliases   │ extension_version │ install_mode │ installed_from │
│     varchar      │ boolean │  boolean  │       varchar        │                      varchar                       │ varchar[]  │      varchar      │   varchar    │    varchar     │
├──────────────────┼─────────┼───────────┼──────────────────────┼────────────────────────────────────────────────────┼────────────┼───────────────────┼──────────────┼────────────────┤
│ postgres_scanner │ false   │ true      │ /Users/stevenwang/…  │ Adds support for connecting to a Postgres database │ [postgres] │ c0411b9           │ REPOSITORY   │ core           │
└──────────────────┴─────────┴───────────┴──────────────────────┴────────────────────────────────────────────────────┴────────────┴───────────────────┴──────────────┴────────────────┘

To Reproduce

attach 'ducklake:postgres:postgresql://postgres:password@host:5432/ducklake_catalog' as my_ducklake (DATA_PATH 'file_path');

OS:

linux_amd64, osx_arm64

PostgreSQL Version:

15.1

DuckDB Version:

1.3.1

DuckDB Client:

CLI

Full Name:

Steven Wang

Affiliation:

definite.app

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