Postgres Pro
Downloads
Home   >   mailing lists

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

From Robert Haas
Subject Re: base backup client as auxiliary backend process
Date
Msg-id CA+TgmoZ_ZGc4gqEEOOX-3bjMPBt4=E0wFYTytVDADJiuo=G7eQ@mail.gmail.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  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
On Sat, Jun 29, 2019 at 4:05 PM Peter Eisentraut
<peter.eisentraut@2ndquadrant.com> wrote:
> My idea is that the postmaster can launch a base backup worker, wait
> till it's done, then proceed with the rest of the startup.  initdb gets
> a special option to create a "minimal" data directory with only a few
> files, directories, and the usual configuration files.

Why do we even have to do that much?  Can we remove the need for an
initdb altogether?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: let's make the list of reportable GUCs configurable (was Re: Add%r substitution for psql prompts to show recovery status)
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] [WIP] Effective storage of duplicates in B-tree index.