diff options
| author | Nathan Bossart <nathan@postgresql.org> | 2023-08-24 10:13:31 -0700 |
|---|---|---|
| committer | Nathan Bossart <nathan@postgresql.org> | 2023-08-24 10:13:31 -0700 |
| commit | 9625845532ae03e7da3fc8fc592c6ec333b93166 (patch) | |
| tree | 0029bcc9a63b5638a49119016a9740ce7a1b4fcb /src/backend/parser/parse_utilcmd.c | |
| parent | d8b2fcc9d4b5af9704dadf00d68859229d9868ad (diff) | |
| download | postgresql-9625845532ae03e7da3fc8fc592c6ec333b93166.tar.gz postgresql-9625845532ae03e7da3fc8fc592c6ec333b93166.zip | |
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
Diffstat (limited to 'src/backend/parser/parse_utilcmd.c')
0 files changed, 0 insertions, 0 deletions