Re: base backup client as auxiliary backend process

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: base backup client as auxiliary backend process
Дата
Msg-id 62e860f2-ae4b-67a1-b65d-04c3d1bf6aff@2ndquadrant.com
обсуждение исходный текст
Ответ на base backup client as auxiliary backend process  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Ответы Re: base backup client as auxiliary backend process  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Re: base backup client as auxiliary backend process  (Michael Paquier <michael@paquier.xyz>)
Список pgsql-hackers
> Attached is a very hackish patch to implement this.  It works like this:
> 
>     # (assuming you have a primary already running somewhere)
>     initdb -D data2 --replica
>     $EDITOR data2/postgresql.conf  # set primary_conninfo
>     pg_ctl -D data2 start

Attached is an updated patch for this.  I have changed the initdb option
name per suggestion.  The WAL receiver is now started concurrently with
the base backup.  There is progress reporting (ps display), fsyncing.
Configuration files are not copied anymore.  There is a simple test
suite.  Tablespace support is still missing, but it would be
straightforward.

It's still all to be considered experimental, but it's taking shape and
working pretty well.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Вложения

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

Предыдущее
От: Konstantin Knizhnik
Дата:
Сообщение: Re: PATCH: logical_work_mem and logical streaming of largein-progress transactions
Следующее
От: Robert Haas
Дата:
Сообщение: Re: block-level incremental backup