| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | 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-27 11:35:56 |
| Message-ID: | d8d691e9-b4cb-b063-a9f1-af8d3d62cac8@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-10-27 11:53, Bruce Momjian 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.
Well, that one can trivially be replaced by a printed instruction, too.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2020-10-27 11:40:00 | Re: Prevent printing "next step instructions" in initdb and pg_upgrade |
| Previous Message | Bruce Momjian | 2020-10-27 11:34:07 | Re: Internal key management system |