Re: small pg_basebackup display bug

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Erik Rijkers <er(at)xs4all(dot)nl>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: small pg_basebackup display bug
Date: 2012-12-16 18:20:53
Message-ID: 17451.1355682053@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Magnus Hagander <magnus(at)hagander(dot)net> writes:
> On Sat, Dec 15, 2012 at 2:24 PM, Erik Rijkers <er(at)xs4all(dot)nl> wrote:
>> That would make such a truncation less frequent, and after all a truncated display is not
>> particular useful.

> Agreed - it's useful during testing, but not in a typical production
> use. It might actually be more useful if it's truncated in in the
> other end (keeping the last 30 instead of the first 30 chars)

+1 for truncating from the left. I think pg_upgrade already does that
in its progress messages.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2012-12-16 18:20:54 Re: multiple CREATE FUNCTION AS items for PLs
Previous Message Hannu Krosing 2012-12-16 18:13:26 Re: multiple CREATE FUNCTION AS items for PLs