Re: [GENERAL] replication slot to be used in the future

Поиск
Список
Период
Сортировка
От Adrian Klaver
Тема Re: [GENERAL] replication slot to be used in the future
Дата
Msg-id 031d8d64-7988-5e52-b59e-cdd38ef51b20@aklaver.com
обсуждение исходный текст
Ответ на [GENERAL] replication slot to be used in the future  (Tom DalPozzo <t.dalpozzo@gmail.com>)
Ответы Re: [GENERAL] replication slot to be used in the future  (Tom DalPozzo <t.dalpozzo@gmail.com>)
Список pgsql-general
On 01/04/2017 08:44 AM, Tom DalPozzo wrote:
> Hi,

Postgres version?

Because in 9.6:

https://www.postgresql.org/docs/9.6/static/functions-admin.html#FUNCTIONS-REPLICATION

Table 9-82. Replication SQL Functions

pg_create_physical_replication_slot(slot_name name [,
immediately_reserve boolean ])

Creates a new physical replication slot named slot_name. The optional
second parameter, when true, specifies that the LSN for this replication
slot be reserved immediately; otherwise the LSN is reserved on first
connection from a streaming replication client. Streaming changes from a
physical slot is only possible with the streaming-replication protocol —
see Section 51.3. This function corresponds to the replication protocol
command CREATE_REPLICATION_SLOT ... PHYSICAL.

> I've got my primary and I make a pg_basebackup -x in order to create a
> standby.
> I can connect my standby only later, in some hours, so I'd like the
> master to keep new WALs but I don't like to use archiving nor
> keep-segments option. I thought to do it through a physical replication
> slot (my standby will have its replication slot name).
> So I create a physical replication slot but I see that the master, which
> has never seen my standby connected to him, doesn't keep WALs.
>
> Any idea?
>
> Regards
> Pupillo
>
>
>
>


--
Adrian Klaver
adrian.klaver@aklaver.com


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

Предыдущее
От: Israel Brewster
Дата:
Сообщение: Re: [GENERAL] Index impact on update?
Следующее
От: DrakoRod
Дата:
Сообщение: [GENERAL] Re: could not load library "$libdir/sslutils": in pg_upgradeprocess