Re: Fix for pg_upgrade status display

Поиск
Список
Период
Сортировка
От Alvaro Herrera
Тема Re: Fix for pg_upgrade status display
Дата
Msg-id 20121206175344.GA4299@alvh.no-ip.org
обсуждение исходный текст
Ответ на Re: Fix for pg_upgrade status display  (Robert Haas <robertmhaas@gmail.com>)
Ответы Re: Fix for pg_upgrade status display
Список pgsql-hackers
Robert Haas escribió:
> 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?

I think this should be keyed off the terminal width, actually, no?  The
whole point of this is to overwrite the same line over and over, right?

--
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: How to check whether the row was modified by this transaction before?
Следующее
От: Jeff Davis
Дата:
Сообщение: Re: Commits 8de72b and 5457a1 (COPY FREEZE)