Feedback-ID: i131946ab:Fastmail
Message-ID: <a623ef37-8b73-dcc2-12a4-fa499097d5c1@enterprisedb.com>
Date: Fri, 27 Jan 2023 08:47:37 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0)
 Gecko/20100101 Thunderbird/102.6.1
Subject: Re: drop postmaster symlink
Content-Language: en-US
To: "Karl O. Pinc" <kop@karlpinc.com>
Cc: =?UTF-8?B?RGV2cmltIEfDvG5kw7x6?= <devrim@gunduz.org>,
 Joe Conway <mail@joeconway.com>, Robert Haas <robertmhaas@gmail.com>,
 Andres Freund <andres@anarazel.de>, Tom Lane <tgl@sss.pgh.pa.us>,
 pgsql-hackers <pgsql-hackers@postgresql.org>
References: <ece84b69-8f94-8b88-925f-64207cb3a2f0@enterprisedb.com>
 <252b8b14-dc3e-1c70-3da5-e59c1616f2ad@joeconway.com>
 <6b11c9efcd3a1d89719370224d84f8cd5e7b1a8c.camel@gunduz.org>
 <3705500.1669216069@sss.pgh.pa.us>
 <20221123195010.huuypoilx6lw7ceg@awork3.anarazel.de>
 <CA+TgmoZdJ3TOBCnoz0x0zzfOtbOR12f1PHLQP8G1U3NEycUgRw@mail.gmail.com>
 <61846051-90b9-adb6-7627-08a374473a61@joeconway.com>
 <63a898b5-dc09-1ec1-40ec-e9d09e8304e7@enterprisedb.com>
 <b46cb741-7856-2410-0c4f-2af9e0fb9892@joeconway.com>
 <05cd2e78dd3b7142f16fd7f14b1694c3520af345.camel@gunduz.org>
 <7165e051-94c7-4e14-ff0a-043b34c67e9e@enterprisedb.com>
 <f6c7bdd1102e9f8b1013a2d4a4552759a695b900.camel@gunduz.org>
 <20230125180325.696f2cd7@slate.karlpinc.com>
 <20230126123638.1e918fef@slate.karlpinc.com>
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
In-Reply-To: <20230126123638.1e918fef@slate.karlpinc.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/a623ef37-8b73-dcc2-12a4-fa499097d5c1%40enterprisedb.com>
Precedence: bulk

On 26.01.23 19:36, Karl O. Pinc wrote:
>> I see a possible problem at line 1,412 of runtime.sgml
> This says:
> 
>   in the postmaster's startup script just before invoking the postmaster.
> 
> Depending on how this is read, it could be interpreted to mean
> that a "postmaster" binary is invoked.  It might be more clear
> to write: ... just before invoking <command>postgres</command>.
> 
> Or it might not be worth bothering about; at this point, probably
> not, but I thought you might want the heads-up anyway.

Good find.  I have adjusted that, and a few more nearby.