From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: base backup client as auxiliary backend process |
Date: | 2019-08-30 19:10:10 |
Message-ID: | 62e860f2-ae4b-67a1-b65d-04c3d1bf6aff@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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 | Content-Type | Size |
---|---|---|
v2-0001-Base-backup-client-as-auxiliary-backend-process.patch | text/plain | 44.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2019-08-31 02:58:53 | Re: block-level incremental backup |
Previous Message | Konstantin Knizhnik | 2019-08-30 15:59:32 | Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions |