Re: base backup client as auxiliary backend process - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: base backup client as auxiliary backend process
Date
Msg-id 62e860f2-ae4b-67a1-b65d-04c3d1bf6aff@2ndquadrant.com
Whole thread Raw
In response to base backup client as auxiliary backend process  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses 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>)
List 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

Attachment

pgsql-hackers by date:

Previous
From: Konstantin Knizhnik
Date:
Subject: Re: PATCH: logical_work_mem and logical streaming of largein-progress transactions
Next
From: Robert Haas
Date:
Subject: Re: block-level incremental backup