[omnibus] platforms, PG versions, binaries, etc.

[wuputah]

This is an omnibus recognition of the targets we don't have yet in order to consolidate these feature requests in one place and avoid duplication of very similar issues.

Operating Systems

• Linux
• Mac
• Windows

Postgres Versions

• ❌ Postgres 12 - EOL is Nov 14, 2024 - Support is not planned
• ❌ Postgres 13 - EOL is Nov 13, 2025 - Support is not planned
• Postgres 14
• Postgres 15
• Postgres 16
• Postgres 17
• ❌ Greenplum 6 - Support is not planned as Greenplum 6 is based on Postgres 9.4.

Platforms

• x86_64
• arm64 / aarch64

Binary package types

• apt -> Ubuntu 22.04, Ubuntu 24.04, Debian bookworm, ...
  • supplied via pgxman, which supports Ubuntu Jammy, Ubuntu Noble, and Debian Bookworm. We may consider publishing packages directly in the future.
• pgxman
• Docker image
• homebrew
• rpm -> RHEL, RockyLinux, ...

[Leo-XM-Zeng]

#180 Postgres 15

[JelteF]

As discussed in person. We won't support PG12 and PG13. And PG14 not for the 0.1.0 release, we might support PG14 for a later release if an external contributor is willing to add initial support for it.

PG15 we'll support once #180 is merged for 0.1.0, but might remove support if it turns out to conflict with some of the future features we want to support.

[JelteF]

Marking this as 0.1.0 stability testing as a reminder, but we won't implement all of the things here for 0.1.0. The only things that we have planned fro 0.1.0 are:

• pgxman
• Docker image
• PG15

[wuputah]

All targets expected for 0.1.0 have been met; removing from milestone. I've also updated the OP.

[Vonng]

Currently, there are three DuckDB-related extensions: duckdb_fdw, pg_mooncake, and pg_duckdb, each using its own version of libduckdb. Consequently, it is not feasible to install these extensions simultaneously. Is there a possibility for pg_duckdb to utilize a standalone libduckdb shared library instead of building its own in the PostgreSQL library directory? Adopting a shared library could significantly reduce compilation times and package sizes, and also eliminate extension conflicts.

I've already facilitated the transition for duckdb_fdw and suggested this approach to the authors of pg_mooncake at thisGitHub issue.

By the way, I have built RPM/DEB packages for all the extensions and hosted them in the ext.pigsty.io repository.