From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | 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-06 15:06:13 |
Message-ID: | 1870066.1601996773@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 Tue, Oct 6, 2020 at 4:31 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Hm, does it matter? I think those wrappers send the output to /dev/null
>> anyway.
> The debian ones don't, because they consider it useful information to the
> user. I'd say that it is, especially in the case of pg_upgrade. (Less so
> about initdb, but still a bit -- especially when creating secondary
> clusters)
> The redhat ones I believe sent it to a logfile, not to /dev/null. Meaning
> it's not in your face, but it still contains incorrect instructions.
OK. FWIW, I'd vote for separate --no-instructions and --no-scripts
switches.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Dmitry Dolgov | 2020-10-06 15:20:39 | Re: Index Skip Scan (new UniqueKeys) |
Previous Message | Magnus Hagander | 2020-10-06 15:04:31 | Re: Prevent printing "next step instructions" in initdb and pg_upgrade |