Re: Use consistent terminology for tablesync slots.

Поиск
Список
Период
Сортировка
От Amit Kapila
Тема Re: Use consistent terminology for tablesync slots.
Дата
Msg-id CAA4eK1LQJDkupW4=eixwQvmCgpmBGcdN0Duwbhi3Ud52z+pSkw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Use consistent terminology for tablesync slots.  (Peter Smith <smithpb2250@gmail.com>)
Список pgsql-hackers
On Wed, Mar 31, 2021 at 6:39 AM Peter Smith <smithpb2250@gmail.com> wrote:
>
> On Tue, Mar 30, 2021 at 8:14 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
> >
> > 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.
> >
>
> PSA patch version 2 updated to use "table synchronization slots" as suggested.
>

Thanks, Pushed!

-- 
With Regards,
Amit Kapila.



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Amit Kapila
Дата:
Сообщение: Re: [PATCH] add concurrent_abort callback for output plugin
Следующее
От: Etsuro Fujita
Дата:
Сообщение: Re: Asynchronous Append on postgres_fdw nodes.