Re: Prevent printing "next step instructions" in initdb and pg_upgrade
Magnus Hagander <magnus@hagander.net>
From: Magnus Hagander <magnus@hagander.net>
To: Bruce Momjian <bruce@momjian.us>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2020-10-27T11:05:25Z
Lists: pgsql-hackers
On Tue, Oct 27, 2020 at 11:53 AM Bruce Momjian <bruce@momjian.us> wrote: > On Tue, Oct 27, 2020 at 11:35:25AM +0100, Peter Eisentraut wrote: > > 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? > > There is still delete_old_cluster.sh. > Yeah, that's the one I was thinking of, but I was looking for something more generic than explicitly saying --no-delete-script. -- Magnus Hagander Me: https://www.hagander.net/ <http://www.hagander.net/> Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
Commits
-
Remove extra Success message at the end of initdb
- e7f429148549 14.0 landed