Re: Prevent printing "next step instructions" in initdb and pg_upgrade
Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Magnus Hagander <magnus@hagander.net>,
PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2020-10-27T10:35:25Z
Lists: pgsql-hackers
On 2020-10-06 12:26, Magnus Hagander wrote: > I went with the name --no-instructions to have the same name for both > initdb and pg_upgrade. The downside is that "no-instructions" also > causes the scripts not to be written in pg_upgrade, which arguably is a > different thing. We could go with "--no-instructions" and > "--no-scripts", but that would leave the parameters different. I also > considered "--no-next-step", but that one didn't quite have the right > ring to me. I'm happy for other suggestions on the parameter names. What scripts are left after we remove the analyze script, as discussed in a different thread? -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Remove extra Success message at the end of initdb
- e7f429148549 14.0 landed