Re: pg_upgrade's object listing

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: pg_upgrade's object listing
Date: 2023-10-27 08:50:02
Message-ID: FD9BEF04-1CBD-4EDF-9184-3AE137444139@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 27 Oct 2023, at 10:44, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:

> I honestly doubt that this sort of message is in any way useful, other
> than for program debugging. Maybe listing databases and perhaps slots
> in verbose mode is OK, but tables? I don't think so.

Outputting this in verbose mode is unlikely to help in regular usage and
instead risk drown out other outputs. It would be more useful to be able to
specify a logfile for objects and keep verbose output for more informational
and actionable messages.

--
Daniel Gustafsson

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message shveta malik 2023-10-27 08:51:56 Re: Synchronizing slots from primary to standby
Previous Message Alvaro Herrera 2023-10-27 08:44:17 Re: pg_upgrade's object listing