aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistproc.c
diff options
context:
space:
mode:
authorMasahiko Sawada <msawada@postgresql.org>2025-02-21 10:23:39 -0800
committerMasahiko Sawada <msawada@postgresql.org>2025-02-21 10:23:39 -0800
commit1aab6805919b84a2f2477132d96f2147ed36150e (patch)
treef4c2e1a63cb89b032eea833a701db711bc50fcde /src/backend/access/gist/gistproc.c
parenta8238f87f980848c2d69c105555c4383e20e7670 (diff)
downloadpostgresql-1aab6805919b84a2f2477132d96f2147ed36150e.tar.gz
postgresql-1aab6805919b84a2f2477132d96f2147ed36150e.zip
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
Diffstat (limited to 'src/backend/access/gist/gistproc.c')
0 files changed, 0 insertions, 0 deletions