| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Fabio Pardi <f(dot)pardi(at)portavita(dot)eu> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-performance(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Fwd: upgrade to PG11 on secondary fails (no initdb was launched) |
| Date: | 2019-06-14 16:16:52 |
| Message-ID: | 20190614161652.GI2480@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-performance |
Greetings,
* Fabio Pardi (f(dot)pardi(at)portavita(dot)eu) wrote:
> I understand that in this thread we are contextualizing in a step by
> step procedure to create a new standby, but I have anyway a few remarks
> about it (and the documentation where it has been copied from) and I
> would be glad if you or somebody else could shed some light on it.
This is not a procedure for creating a new standby.
To create a *new* standby, with the primary online, use pg_basebackup or
another tool that knows how to issue the appropriate start/stop backup
and takes care of the WAL.
Thanks!
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Avin Kavish | 2019-06-16 14:26:52 | I want the elephant back |
| Previous Message | Stephen Frost | 2019-06-14 16:15:38 | Re: Fwd: upgrade to PG11 on secondary fails (no initdb was launched) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-06-17 02:01:07 | Re: wal_log_hints benchmarks |
| Previous Message | Stephen Frost | 2019-06-14 16:15:38 | Re: Fwd: upgrade to PG11 on secondary fails (no initdb was launched) |