Re: Add new protocol message to change GUCs for usage with future protocol-only GUCs

Jelte Fennema-Nio <me@jeltef.nl>

From: Jelte Fennema-Nio <me@jeltef.nl>

To: Jacob Burroughs <jburroughs@instructure.com>

Cc: Robert Haas <robertmhaas@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Dave Cramer <davecramer@gmail.com>, "Andrey M. Borodin" <x4mmm@yandex-team.ru>, Pavel Stehule <pavel.stehule@gmail.com>, Jeff Davis <pgsql@j-davis.com>, Peter Eisentraut <peter@eisentraut.org>

Date: 2024-01-05T15:13:48Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

libpq: Add min/max_protocol_version connection options
- 285613c60a7a 18.0 landed
libpq: Handle NegotiateProtocolVersion message differently
- 5070349102af 18.0 landed
Add PQfullProtocolVersion() to surface the precise protocol version.
- cdb6b0fdb0b2 18.0 landed
Do not hardcode PG_PROTOCOL_LATEST in NegotiateProtocolVersion
- 516b87502dc1 18.0 landed
libpq: Handle NegotiateProtocolVersion message
- bbf9c282ce92 16.0 cited
Provide for forward compatibility with future minor protocol versions.
- ae65f6066dc3 11.0 cited

Attachments

v4-0005-Bump-protocol-version-to-3.1.patch (application/octet-stream) patch v4-0005
v4-0002-libpq-Handle-NegotiateProtocolVersion-message-mor.patch (application/octet-stream) patch v4-0002
v4-0004-Prepare-server-code-for-addition-of-protocol-exte.patch (application/octet-stream) patch v4-0004
v4-0003-libpq-Include-minor-version-number-in-PQprotocolV.patch (application/octet-stream) patch v4-0003
v4-0001-libpq-Remove-instance-of-hardcoded-protocol-versi.patch (application/octet-stream) patch v4-0001
v4-0006-Add-_pq_.protocol_managed_params-protocol-extensi.patch (application/octet-stream) patch v4-0006
v4-0007-Add-protcol-message-to-change-protocol-extension-.patch (application/octet-stream) patch v4-0007

New patchset attached, where I split up the patches in smaller logical units.
Note that the first 4 patches in this series are not making any
protocol changes. All they do is set up infrastructure in the code
that allows us to make protocol changes in the future.

I hope that those 4 should all be fairly uncontroversial, especially
patch 1 seems a no-brainer to me. Note that this infrastructure would
be needed for any patchset that introduces protocol changes.

The 5th only bumps the version

The 6th introduces the _pq_.protocol_managed_parms protocol parameter

The 7th adds the new ParameterSet protocol message