Re: base backup client as auxiliary backend process
От | Peter Eisentraut |
---|---|
Тема | Re: base backup client as auxiliary backend process |
Дата | |
Msg-id | 7925a361-d48c-db03-30b4-fcd331ef7f02@2ndquadrant.com обсуждение исходный текст |
Ответ на | Re: base backup client as auxiliary backend process (Masahiko Sawada <masahiko.sawada@2ndquadrant.com>) |
Ответы |
Re: base backup client as auxiliary backend process
Re: base backup client as auxiliary backend process |
Список | pgsql-hackers |
On 2020-01-14 07:32, Masahiko Sawada wrote: > - <entry>Replication slot name used by this WAL receiver</entry> > + <entry> > + Replication slot name used by this WAL receiver. This is only set if a > + permanent replication slot is set using <xref > + linkend="guc-primary-slot-name"/>. Otherwise, the WAL receiver may use > + a temporary replication slot (determined by <xref > + linkend="guc-wal-receiver-create-temp-slot"/>), but these are not shown > + here. > + </entry> > > Now that the slot name is shown even if it's a temp slot the above > documentation changes needs to be changed. Other changes look good to > me. committed, thanks -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: