From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Dan Stoner <dstoner@iris.washington.edu>
To: pgsql-docs@lists.postgresql.org
Subject: Re: No mention of standby.signal in pg_ugprade docs
Date: Fri, 16 Jul 2021 07:19:48 +0200
Message-ID: <f0b2a275d5e1ba839cbef9e78eb63802c3c76b24.camel@cybertec.at> (raw)
In-Reply-To: <1A5A1B6E-7BB6-47EB-8443-40222B769404@iris.washington.edu>
References: <1A5A1B6E-7BB6-47EB-8443-40222B769404@iris.washington.edu>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: laurenz.albe@cybertec.at, dstoner@iris.washington.edu, pgsql-docs@lists.postgresql.org
Subject: Re: No mention of standby.signal in pg_ugprade docs
In-Reply-To: <f0b2a275d5e1ba839cbef9e78eb63802c3c76b24.camel@cybertec.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox