Date: Sat, 12 Sep 2020 10:45:50 +0900
From: Michael Paquier <michael@paquier.xyz>
To: Robert Treat <rob@xzilla.net>
Cc: pgsql-docs@postgresql.org
Subject: Re: replication wordsmithing / clarifications
Message-ID: <20200912014550.GL2743@paquier.xyz>
References: 
 <CAJSLCQ2TPaK_K8raofCamrqELCxY-H6mJrpDNRzc-LKpPY7c+g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="kkcDP0v44wDpNmbp"
Content-Disposition: inline
In-Reply-To: 
 <CAJSLCQ2TPaK_K8raofCamrqELCxY-H6mJrpDNRzc-LKpPY7c+g@mail.gmail.com>
Precedence: bulk


--kkcDP0v44wDpNmbp
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Fri, Sep 11, 2020 at 07:16:43PM -0400, Robert Treat wrote:
> A recent discussion on slack prompted me to read through the
> high-availability section of the docs, turning in to some suggested
> changes that hopefully clarify how the various replication options
> work (specifically around logical and trigger-based solutions). A
> proposed patch is attached, lmk if you have questions.

A portion of what you are suggesting here is in line with 9e101cf,
which looks like a good thing.  Most of the changes look like
improvements to me, and here are some comments.

+     queries to a designated primary server. Operating on a per-tablebasis,
+     the primary server sends data changes (typically) asynchronously to the
+     replica node(s).  Replica nodes can answer queries while the primary is
Could it be better to use "one or more replica clusters" here?

      This is because each server operates independently, and because
-     SQL queries are broadcast (and not actual modified rows). If
+     SQL queries are broadcast rather than actual data changes.  If
      this is unacceptable, either the middleware or the application
-     must query such values from a single server and then use those
-     values in write queries.  Another option is to use this replication
-     option with a traditional primary-standby setup, i.e., data modification
-     queries are sent only to the primary and are propagated to the
-     standby servers via primary-standby replication, not by the replication
-     middleware.  Care must also be taken that all
+     must determine such values from a single source and then use those
+     values in write queries.  Care must also be taken that all
Why do you remove the sentence about the extra option available to the
user here, about the traditional primary-standby setup?
--
Michael

--kkcDP0v44wDpNmbp
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAl9cKE4ACgkQnvQgOdby
QH25YA/9EwmMFvPsAhalBABRA+hn4a/CICFUDnAMGnLqUsNNVib1+kbvsNSED0kQ
A+XQgtiD+1jQY5ZT7t1QvO9KY3C8Hac38KMSywrlGsF6x4sWznNyv/LGxikAeWdk
XWQ70M7hYftzl9bGpKIHNGczHQVtQ5hHhcMZEWpCEpktuvdQiBmhH8O9mB0Awkl/
7rRaHXX7gIrQ48GJkwk8s021Lpv3sR5VmQ/LRxs8Gewd9eGlXDet40HmluWcPrH6
ViSiB7axcpz6NffiZsdTNa5wqr8m+xiBqZFK4JRz7U8YqZAhTT6LD1zGscZnTnYl
x+YITyZST8EZPCEKX7izBcf9RmcoriKEjF0SSwor4xOmGJRuQErJTmjCMkFDWjJf
Iy5MWHbhOlwIGR/gUbPhM3wkK1y/rS7B798+yLLACge2nU0t44o/SoW8Y2cAmDEk
L1ObPg3LCvvKNtUupDI8ADXoA6tMDYSSCnRu2zWIXPXEVMKU7zUIH9VhH0kBnYfZ
BVsKLYdn+EAN5UDhc60M04Ekq3M3jrMzVCvKfSxbfpKRgJPHmjvDSl/5Bo5iCRmC
PjmH/+9Vy/BHE+ZHQ2in5RSdeff8UUe15idrir9ApXzMeDToQhGJuPoXIBEuMeli
Yg3ncJLwh/CLRS3hXr++LBQIsuGk9toySqcs3tDjv33A2buewMI=
=2GcH
-----END PGP SIGNATURE-----

--kkcDP0v44wDpNmbp--