| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: base backup client as auxiliary backend process |
| Date: | 2019-07-11 14:36:43 |
| Message-ID: | 24131.1562855803@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Sat, Jun 29, 2019 at 4:05 PM Peter Eisentraut
> <peter(dot)eisentraut(at)2ndquadrant(dot)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?
Gotta have config files in place already, no?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2019-07-11 14:59:32 | Re: [sqlsmith] Crash in mcv_get_match_bitmap |
| Previous Message | Tom Lane | 2019-07-11 14:35:50 | Re: let's make the list of reportable GUCs configurable (was Re: Add %r substitution for psql prompts to show recovery status) |