summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNathan Bossart <nathan@postgresql.org>2023-08-24 10:13:31 -0700
committerNathan Bossart <nathan@postgresql.org>2023-08-24 10:13:45 -0700
commit2e7d15ab69d91abc874f6b5d89df4d7c5a4f2c17 (patch)
tree27de7926c8c46a3024352d69b51814d49f3adeb2
parentba0d737caa44d322c709c4d64e95de86b126f3e4 (diff)
pg_upgrade: Bump MESSAGE_WIDTH.
Commit 7b378237aa added a status message to pg_upgrade that is 60 characters wide. Since the MESSAGE_WIDTH macro is currently set to 60, there is no space between this new status message and the "ok" or "failed" indicator appended when the step completes. To fix this problem, this commit increases the value of MESSAGE_WIDTH to 62. Suggested-by: Bharath Rupireddy Reviewed-by: Peter Eisentraut Discussion: https://postgr.es/m/CALj2ACVVvk1cYLtWVxHv%3DZ1Ubq%3DUES9fhKbUU4c9k4W%2BfEDnbw%40mail.gmail.com Backpatch-through: 16
-rw-r--r--src/bin/pg_upgrade/pg_upgrade.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/bin/pg_upgrade/pg_upgrade.h b/src/bin/pg_upgrade/pg_upgrade.h
index 3eea0139c74..7afa96716ec 100644
--- a/src/bin/pg_upgrade/pg_upgrade.h
+++ b/src/bin/pg_upgrade/pg_upgrade.h
@@ -22,7 +22,7 @@
#define MAX_STRING 1024
#define QUERY_ALLOC 8192
-#define MESSAGE_WIDTH 60
+#define MESSAGE_WIDTH 62
#define GET_MAJOR_VERSION(v) ((v) / 100)