Horton

pg_upgrade: Add --set-char-signedness to set the default char signedness of new cluster.

Masahiko Sawada <msawada@postgresql.org>

View on postgr.es
Commit: 1aab6805919b84a2f2477132d96f2147ed36150e
Author: Masahiko Sawada <msawada@postgresql.org>
Date: 2025-02-21T18:23:39Z
Releases: 18.0 
pg_upgrade: Add --set-char-signedness to set the default char signedness of new cluster.

This change adds a new option --set-char-signedness to pg_upgrade. It
enables user to set arbitrary signedness during pg_upgrade. This helps
cases where user who knew they copied the v17 source cluster from
x86 (signedness=true) to ARM (signedness=false) can pg_upgrade
properly without the prerequisite of acquiring an x86 VM.

Reviewed-by: Noah Misch <noah@leadboat.com>
Discussion: https://postgr.es/m/CB11ADBC-0C3F-4FE0-A678-666EE80CBB07%40amazon.com

Files

PathChange+/−
doc/src/sgml/ref/pgupgrade.sgml modified +53 −0
src/bin/pg_upgrade/check.c modified +12 −0
src/bin/pg_upgrade/option.c modified +12 −0
src/bin/pg_upgrade/pg_upgrade.c modified +8 −2
src/bin/pg_upgrade/pg_upgrade.h modified +3 −0
src/bin/pg_upgrade/t/005_char_signedness.pl modified +17 −0

Documentation touched

Discussion