Postgres Pro
Downloads
Home   >   mailing lists

Re: Use consistent terminology for tablesync slots. - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Use consistent terminology for tablesync slots.
Date
Msg-id CAA4eK1+Hdk1R9hT=1DWH_utgcSPT+rkciUMM5jvMCmVVEbE1_A@mail.gmail.com
Whole thread Raw
In response to Use consistent terminology for tablesync slots.  (Peter Smith <smithpb2250@gmail.com>)
Responses Re: Use consistent terminology for tablesync slots.  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
Re: Use consistent terminology for tablesync slots.  (Peter Smith <smithpb2250@gmail.com>)
List pgsql-hackers
Tree view 
On Tue, Mar 30, 2021 at 2:21 PM Peter Smith <smithpb2250@gmail.com> wrote:
>
> Hi,
>
> The logical replication tablesync worker creates tablesync slots.
>
> Previously some PG docs pages were referring to these as "tablesync
> slots", but other pages called them as "table synchronization slots".
>
> PSA a trivial patch which (for consistency) now calls them all the
> same -  "tablesync slots"
>

+1 for the consistency. But I think it better to use "table
synchronization slots" in the user-facing docs as that makes it easier
for users to understand.

-- 
With Regards,
Amit Kapila.

pgsql-hackers by date:

Previous
From: Ajin Cherian
Date:
Subject: Re: [PATCH] add concurrent_abort callback for output plugin
Next
From: Peter Eisentraut
Date:
Subject: Re: Add Nullif case for eval_const_expressions_mutator