Matthias van de Meent 6c6de6382a Use enum-typed PG versions (#12317) ...

This makes it possible for the compiler to validate that a match block
matched all PostgreSQL versions we support.

## Problem
We did not have a complete picture about which places we had to test
against PG versions, and what format these versions were: The full PG
version ID format (Major/minor/bugfix `MMmmbb`) as transfered in
protocol messages, or only the Major release version (`MM`). This meant
type confusion was rampant.

With this change, it becomes easier to develop new version-dependent
features, by making type and niche confusion impossible.

## Summary of changes
Every use of `pg_version` is now typed as either `PgVersionId` (u32,
valued in decimal `MMmmbb`) or PgMajorVersion (an enum, with a value for
every major version we support, serialized and stored like a u32 with
the value of that major version)

---------

Co-authored-by: Arpad Müller <arpad-m@users.noreply.github.com>

2025-06-24 17:25:31 +00:00

..

src

Use enum-typed PG versions (#12317)

2025-06-24 17:25:31 +00:00

Cargo.toml

Use enum-typed PG versions (#12317)

2025-06-24 17:25:31 +00:00