Re: Prevent printing "next step instructions" in initdb and pg_upgrade - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Prevent printing "next step instructions" in initdb and pg_upgrade
Date
Msg-id 20201124152829.GD29448@momjian.us
Whole thread Raw
In response to Re: Prevent printing "next step instructions" in initdb and pg_upgrade  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
On Tue, Nov 24, 2020 at 04:05:26PM +0100, Magnus Hagander wrote:
> pg_upgrade is a somewhat different but also interesting case. I think
> the actual progress output is more interesting in pg_upgrade as it's
> more likely to take measurable amounts of time. Whereas in initdb,
> it's actually the "detected parameter values" that are the most
> interesting parts.

Originally, initdb did take some time for each step.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EnterpriseDB                             https://enterprisedb.com

  The usefulness of a cup is in its emptiness, Bruce Lee




pgsql-hackers by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: abstract Unix-domain sockets
Next
From: Peter Eisentraut
Date:
Subject: Re: abstract Unix-domain sockets