Re: base backup client as auxiliary backend process
Thomas Munro <thomas.munro@gmail.com>
From: Thomas Munro <thomas.munro@gmail.com>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2019-07-05T03:07:40Z
Lists: pgsql-hackers
On Sun, Jun 30, 2019 at 8:05 AM Peter Eisentraut <peter.eisentraut@2ndquadrant.com> wrote: > Attached is a very hackish patch to implement this. It works like this: > > # (assuming you have a primary already running somewhere) > initdb -D data2 --minimal > $EDITOR data2/postgresql.conf # set primary_conninfo > pg_ctl -D data2 start +1, very nice. How about --replica? FIY Windows doesn't like your patch: src/backend/postmaster/postmaster.c(1396): warning C4013: 'sleep' undefined; assuming extern returning int [C:\projects\postgresql\postgres.vcxproj] https://ci.appveyor.com/project/postgresql-cfbot/postgresql/build/1.0.45930 -- Thomas Munro https://enterprisedb.com
Commits
-
Factor out InitControlFile() from BootStrapXLOG()
- 79c2385915dd 13.0 landed
-
Reformat code comment
- 9745f93afc56 13.0 landed
-
pg_resetwal: Rename function to avoid potential conflict
- 5f1b8260af96 13.0 landed
-
Expose PQbackendPID() through walreceiver API
- ee4ac46c8eb2 13.0 landed
-
walreceiver uses a temporary replication slot by default
- 329730827848 13.0 landed
-
Make lsn argument of walrcv_create_slot() optional
- c67a55da4ea0 13.0 landed
-
More precise errors from initial pg_control check
- b85e43feb3e8 13.0 landed