Re: Fix for pg_upgrade status display - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Fix for pg_upgrade status display
Date
Msg-id CA+TgmoYQ61GXAkOOK9tLw1Fph9kUo9ULAD0WoO7Mxe6Gyvz=WQ@mail.gmail.com
Whole thread Raw
In response to Fix for pg_upgrade status display  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Fix for pg_upgrade status display
Re: Fix for pg_upgrade status display
List pgsql-hackers
On Wed, Dec 5, 2012 at 10:04 PM, Bruce Momjian <bruce@momjian.us> wrote:
> Pg_upgrade displays file names during copy and database names during
> dump/restore.  Andrew Dunstan identified three bugs:
>
> *  long file names were being truncated to 60 _leading_ characters, which
> often do not change for long file names
>
> *  file names were truncated to 60 characters in log files
>
> *  carriage returns were being output to log files
>
> The attached patch fixes these --- it prints 60 _trailing_ characters to
> the status display, and full path names without carriage returns to log
> files.

This might be a dumb question, but why limit it to 60 characters at
all instead of, say, MAXPGPATH?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Serious problem: media recovery fails after system or PostgreSQL crash
Next
From: Robert Haas
Date:
Subject: Re: autovacuum truncate exclusive lock round two