Message-ID: <f0b2a275d5e1ba839cbef9e78eb63802c3c76b24.camel@cybertec.at>
Subject: Re: No mention of standby.signal in pg_ugprade docs
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Dan Stoner <dstoner@iris.washington.edu>, pgsql-docs@lists.postgresql.org
Date: Fri, 16 Jul 2021 07:19:48 +0200
In-Reply-To: <1A5A1B6E-7BB6-47EB-8443-40222B769404@iris.washington.edu>
References: <1A5A1B6E-7BB6-47EB-8443-40222B769404@iris.washington.edu>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.36.5 (3.36.5-2.fc32) 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/f0b2a275d5e1ba839cbef9e78eb63802c3c76b24.camel%40cybertec.at>
Precedence: bulk

On Thu, 2021-07-15 at 14:39 -0400, Dan Stoner wrote:
> I noticed that  standby.signal is not mentioned anywhere in the pg_upgrade document.
> 
> https://www.postgresql.org/docs/13/pgupgrade.html
> 
> I had trouble the first time I tried to start my secondary because it didn't connect to the primary / start streaming until I touched the signal 
> file.  The signal file is obliterated during the rsync but there is no mention of putting it back or preserving it.

I think you are right.

I will incorporate that in my patch to improve the documentation:
https://www.postgr.es/m/22f129004bb66cd91e1dfd3345a9787f5039f3ae.camel%40cybertec.at

Yours,
Laurenz Albe