Re: Prevent printing "next step instructions" in initdb and pg_upgrade

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Prevent printing "next step instructions" in initdb and pg_upgrade
Date: 2020-10-07 01:45:07
Message-ID: 20201007014507.GC2256@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Oct 06, 2020 at 11:22:11AM -0400, Bruce Momjian wrote:
> On Tue, Oct 6, 2020 at 11:06:13AM -0400, Tom Lane wrote:
>> OK. FWIW, I'd vote for separate --no-instructions and --no-scripts
>> switches.
>
> Works for me.

+1.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2020-10-07 01:53:46 Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view?
Previous Message Michael Paquier 2020-10-07 01:42:49 Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view?