Skip to content

Max version discrepancy between pg_duckdb <> pgxman <> PostgreSQL #944

@wasd171

Description

@wasd171

What happens?

  • Current PostgreSQL version is 18.0 (releases)
  • pg_duckdb supports PostgreSQL v18
  • pgxman support ends at PostgreSQL v16 – 2 major version difference from the current PostgreSQL

This means that for PostgreSQL 17+ it is needed to build pg_duckdb from source, which is definitely not ideal. Given that pgxman is apt-based, it should be feasible to publish a standalone .deb package during the release process. In my opinion, this is something that could help pg_duckdb's adoption

To Reproduce

N/A

OS:

Linux

pg_duckdb Version (if built from source use commit hash):

1.0.0

Postgres Version (if built from source use commit hash):

17-18

Hardware:

No response

Full Name:

Konstantin Nesterov

Affiliation:

CareerLunch AG

What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.

I have tested with a stable release

Did you include all relevant data sets for reproducing the issue?

Not applicable - the reproduction does not require a data set

Did you include all code required to reproduce the issue?

  • Yes, I have

Did you include all relevant configuration (e.g., CPU architecture, Linux distribution) to reproduce the issue?

  • Yes, I have

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions