pgsql: pg_upgrade: Bump MESSAGE_WIDTH.

From: Nathan Bossart <nathan(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: pg_upgrade: Bump MESSAGE_WIDTH.
Date: 2023-08-24 17:14:29
Message-ID: E1qZDuf-000gyj-07@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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

Branch
------
REL_16_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/2e7d15ab69d91abc874f6b5d89df4d7c5a4f2c17

Modified Files
--------------
src/bin/pg_upgrade/pg_upgrade.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Andrew Dunstan 2023-08-24 20:25:20 pgsql: Include header file inadvertently missed in commit 2d13dab048
Previous Message Tom Lane 2023-08-24 16:03:16 pgsql: Avoid unnecessary plancache revalidation of utility statements.