pgsql: Doc: Use consistent terminology for tablesync slots.

From: Amit Kapila <akapila(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Doc: Use consistent terminology for tablesync slots.
Date: 2021-03-31 02:50:17
Message-ID: E1lRQvx-0005ZN-SD@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Doc: Use consistent terminology for tablesync slots.

At some places in the docs, we refer to them as tablesync slots and at other
places as table synchronization slots. For consistency, we refer to them as
table synchronization slots at all places.

Author: Peter Smith
Reviewed-by: Amit Kapila
Discussion: https://postgr.es/m/CAHut+PvzYNKCeZ=kKBDkh3dw-r=2D3fk=nNc9SXSW=CZGk69xg@mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/9f45631766bd0c51a74102770737ba3b0561977e

Modified Files
--------------
doc/src/sgml/ref/alter_subscription.sgml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2021-03-31 03:31:05 Re: pgsql: Add unistr function
Previous Message Noah Misch 2021-03-31 01:55:03 pgsql: Accept slightly-filled pages for tuples larger than fillfactor.