public inbox for [email protected]
help / color / mirror / Atom feedpgsql: pg_upgrade: Use max_protocol_version=3.0 for older servers
6+ messages / 1 participants
[nested] [flat]
* pgsql: pg_upgrade: Use max_protocol_version=3.0 for older servers
@ 2026-02-24 22:33 Jacob Champion <[email protected]>
0 siblings, 0 replies; 6+ messages in thread
From: Jacob Champion @ 2026-02-24 22:33 UTC (permalink / raw)
To: [email protected]
pg_upgrade: Use max_protocol_version=3.0 for older servers
The grease patch in 4966bd3ed found its first problem: prior to the
February 2018 patch releases, no server knew how to negotiate protocol
versions, so pg_upgrade needs to take that into account when speaking to
those older servers.
This will be true even after the grease feature is reverted; we don't
need anyone to trip over this again in the future. Backpatch so that all
supported versions of pg_upgrade can gracefully handle an update to the
default protocol version. (This is needed for any distributions that
link older binaries against newer libpqs, such as Debian.) Branches
prior to 18 need an additional version check, for the existence of
max_protocol_version.
Per buildfarm member crake.
Reviewed-by: Tom Lane <[email protected]>
Discussion: https://postgr.es/m/CAOYmi%2B%3D4QhCjssfNEoZVK8LPtWxnfkwT5p-PAeoxtG9gpNjqOQ%40mail.gmail.com
Backpatch-through: 14
Branch
------
REL_16_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/a38ed212ff236e4e1c94c790d9b9d18f52d2b13a
Modified Files
--------------
src/bin/pg_upgrade/dump.c | 6 +++++-
src/bin/pg_upgrade/pg_upgrade.h | 1 +
src/bin/pg_upgrade/server.c | 2 ++
src/bin/pg_upgrade/version.c | 31 +++++++++++++++++++++++++++++++
4 files changed, 39 insertions(+), 1 deletion(-)
^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: pg_upgrade: Use max_protocol_version=3.0 for older servers
@ 2026-02-24 22:33 Jacob Champion <[email protected]>
0 siblings, 0 replies; 6+ messages in thread
From: Jacob Champion @ 2026-02-24 22:33 UTC (permalink / raw)
To: [email protected]
pg_upgrade: Use max_protocol_version=3.0 for older servers
The grease patch in 4966bd3ed found its first problem: prior to the
February 2018 patch releases, no server knew how to negotiate protocol
versions, so pg_upgrade needs to take that into account when speaking to
those older servers.
This will be true even after the grease feature is reverted; we don't
need anyone to trip over this again in the future. Backpatch so that all
supported versions of pg_upgrade can gracefully handle an update to the
default protocol version. (This is needed for any distributions that
link older binaries against newer libpqs, such as Debian.) Branches
prior to 18 need an additional version check, for the existence of
max_protocol_version.
Per buildfarm member crake.
Reviewed-by: Tom Lane <[email protected]>
Discussion: https://postgr.es/m/CAOYmi%2B%3D4QhCjssfNEoZVK8LPtWxnfkwT5p-PAeoxtG9gpNjqOQ%40mail.gmail.com
Backpatch-through: 14
Branch
------
REL_15_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/e726620d208ee1fca37a6cbfe0fc9a7031ff659e
Modified Files
--------------
src/bin/pg_upgrade/dump.c | 6 +++++-
src/bin/pg_upgrade/pg_upgrade.h | 1 +
src/bin/pg_upgrade/server.c | 2 ++
src/bin/pg_upgrade/version.c | 31 +++++++++++++++++++++++++++++++
4 files changed, 39 insertions(+), 1 deletion(-)
^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: pg_upgrade: Use max_protocol_version=3.0 for older servers
@ 2026-02-24 22:33 Jacob Champion <[email protected]>
0 siblings, 0 replies; 6+ messages in thread
From: Jacob Champion @ 2026-02-24 22:33 UTC (permalink / raw)
To: [email protected]
pg_upgrade: Use max_protocol_version=3.0 for older servers
The grease patch in 4966bd3ed found its first problem: prior to the
February 2018 patch releases, no server knew how to negotiate protocol
versions, so pg_upgrade needs to take that into account when speaking to
those older servers.
This will be true even after the grease feature is reverted; we don't
need anyone to trip over this again in the future. Backpatch so that all
supported versions of pg_upgrade can gracefully handle an update to the
default protocol version. (This is needed for any distributions that
link older binaries against newer libpqs, such as Debian.) Branches
prior to 18 need an additional version check, for the existence of
max_protocol_version.
Per buildfarm member crake.
Reviewed-by: Tom Lane <[email protected]>
Discussion: https://postgr.es/m/CAOYmi%2B%3D4QhCjssfNEoZVK8LPtWxnfkwT5p-PAeoxtG9gpNjqOQ%40mail.gmail.com
Backpatch-through: 14
Branch
------
REL_17_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/ad7fc3f1f83f776812af27dbb747642dc88bba78
Modified Files
--------------
src/bin/pg_upgrade/dump.c | 6 +++++-
src/bin/pg_upgrade/pg_upgrade.h | 1 +
src/bin/pg_upgrade/server.c | 2 ++
src/bin/pg_upgrade/version.c | 31 +++++++++++++++++++++++++++++++
4 files changed, 39 insertions(+), 1 deletion(-)
^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: pg_upgrade: Use max_protocol_version=3.0 for older servers
@ 2026-02-24 22:33 Jacob Champion <[email protected]>
0 siblings, 0 replies; 6+ messages in thread
From: Jacob Champion @ 2026-02-24 22:33 UTC (permalink / raw)
To: [email protected]
pg_upgrade: Use max_protocol_version=3.0 for older servers
The grease patch in 4966bd3ed found its first problem: prior to the
February 2018 patch releases, no server knew how to negotiate protocol
versions, so pg_upgrade needs to take that into account when speaking to
those older servers.
This will be true even after the grease feature is reverted; we don't
need anyone to trip over this again in the future. Backpatch so that all
supported versions of pg_upgrade can gracefully handle an update to the
default protocol version. (This is needed for any distributions that
link older binaries against newer libpqs, such as Debian.) Branches
prior to 18 need an additional version check, for the existence of
max_protocol_version.
Per buildfarm member crake.
Reviewed-by: Tom Lane <[email protected]>
Discussion: https://postgr.es/m/CAOYmi%2B%3D4QhCjssfNEoZVK8LPtWxnfkwT5p-PAeoxtG9gpNjqOQ%40mail.gmail.com
Backpatch-through: 14
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/a60a103386a1e8bde65fa80feb2486d23bacbbcd
Modified Files
--------------
src/bin/pg_upgrade/dump.c | 6 +++++-
src/bin/pg_upgrade/pg_upgrade.h | 1 +
src/bin/pg_upgrade/server.c | 2 ++
src/bin/pg_upgrade/task.c | 2 ++
src/bin/pg_upgrade/version.c | 18 ++++++++++++++++++
5 files changed, 28 insertions(+), 1 deletion(-)
^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: pg_upgrade: Use max_protocol_version=3.0 for older servers
@ 2026-02-24 22:33 Jacob Champion <[email protected]>
0 siblings, 0 replies; 6+ messages in thread
From: Jacob Champion @ 2026-02-24 22:33 UTC (permalink / raw)
To: [email protected]
pg_upgrade: Use max_protocol_version=3.0 for older servers
The grease patch in 4966bd3ed found its first problem: prior to the
February 2018 patch releases, no server knew how to negotiate protocol
versions, so pg_upgrade needs to take that into account when speaking to
those older servers.
This will be true even after the grease feature is reverted; we don't
need anyone to trip over this again in the future. Backpatch so that all
supported versions of pg_upgrade can gracefully handle an update to the
default protocol version. (This is needed for any distributions that
link older binaries against newer libpqs, such as Debian.) Branches
prior to 18 need an additional version check, for the existence of
max_protocol_version.
Per buildfarm member crake.
Reviewed-by: Tom Lane <[email protected]>
Discussion: https://postgr.es/m/CAOYmi%2B%3D4QhCjssfNEoZVK8LPtWxnfkwT5p-PAeoxtG9gpNjqOQ%40mail.gmail.com
Backpatch-through: 14
Branch
------
REL_18_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/1b2773179f31b25bc560e06a35970fdd9b1a6d90
Modified Files
--------------
src/bin/pg_upgrade/dump.c | 6 +++++-
src/bin/pg_upgrade/pg_upgrade.h | 1 +
src/bin/pg_upgrade/server.c | 2 ++
src/bin/pg_upgrade/task.c | 2 ++
src/bin/pg_upgrade/version.c | 18 ++++++++++++++++++
5 files changed, 28 insertions(+), 1 deletion(-)
^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: pg_upgrade: Use max_protocol_version=3.0 for older servers
@ 2026-02-24 22:33 Jacob Champion <[email protected]>
0 siblings, 0 replies; 6+ messages in thread
From: Jacob Champion @ 2026-02-24 22:33 UTC (permalink / raw)
To: [email protected]
pg_upgrade: Use max_protocol_version=3.0 for older servers
The grease patch in 4966bd3ed found its first problem: prior to the
February 2018 patch releases, no server knew how to negotiate protocol
versions, so pg_upgrade needs to take that into account when speaking to
those older servers.
This will be true even after the grease feature is reverted; we don't
need anyone to trip over this again in the future. Backpatch so that all
supported versions of pg_upgrade can gracefully handle an update to the
default protocol version. (This is needed for any distributions that
link older binaries against newer libpqs, such as Debian.) Branches
prior to 18 need an additional version check, for the existence of
max_protocol_version.
Per buildfarm member crake.
Reviewed-by: Tom Lane <[email protected]>
Discussion: https://postgr.es/m/CAOYmi%2B%3D4QhCjssfNEoZVK8LPtWxnfkwT5p-PAeoxtG9gpNjqOQ%40mail.gmail.com
Backpatch-through: 14
Branch
------
REL_14_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/c47744ede01c45dcf73c420a4fc393965909c8ab
Modified Files
--------------
src/bin/pg_upgrade/dump.c | 6 +++++-
src/bin/pg_upgrade/pg_upgrade.h | 1 +
src/bin/pg_upgrade/server.c | 2 ++
src/bin/pg_upgrade/version.c | 31 +++++++++++++++++++++++++++++++
4 files changed, 39 insertions(+), 1 deletion(-)
^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2026-02-24 22:33 UTC | newest]
Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2026-02-24 22:33 pgsql: pg_upgrade: Use max_protocol_version=3.0 for older servers Jacob Champion <[email protected]>
2026-02-24 22:33 pgsql: pg_upgrade: Use max_protocol_version=3.0 for older servers Jacob Champion <[email protected]>
2026-02-24 22:33 pgsql: pg_upgrade: Use max_protocol_version=3.0 for older servers Jacob Champion <[email protected]>
2026-02-24 22:33 pgsql: pg_upgrade: Use max_protocol_version=3.0 for older servers Jacob Champion <[email protected]>
2026-02-24 22:33 pgsql: pg_upgrade: Use max_protocol_version=3.0 for older servers Jacob Champion <[email protected]>
2026-02-24 22:33 pgsql: pg_upgrade: Use max_protocol_version=3.0 for older servers Jacob Champion <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox