From: | Pierre Timmermans <ptim007(at)yahoo(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: using pg_basebackup for point in time recovery |
Date: | 2018-06-21 20:12:06 |
Message-ID: | 2062174856.505174.1529611926021@mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi Michael
On Thursday, June 21, 2018, 7:28:13 AM GMT+2, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>You should avoid top-posting on the Postgres lists, this is not the
>usual style used by people around :)
Will do, but Yahoo Mail! does not seem to like that, so I am typing the > myself
>Attached is a patch which includes your suggestion. What do you think?
>As that's an improvement, only HEAD would get that clarification.
Yes I think it is now perfectly clear. Much appreciated to have the chance to contribute to the doc by the way, it is very nice
>Perhaps. There is really nothing preventing one to add a recovery.conf
>afterwards, which is also why pg_basebackup -R exists. I do that as
>well for some of the framework I work with and maintain.
I just went to the doc to check about this -R option :-)
Pierre
From | Date | Subject | |
---|---|---|---|
Next Message | Ravi Krishna | 2018-06-21 20:42:00 | Re: using pg_basebackup for point in time recovery |
Previous Message | Moreno Andreo | 2018-06-21 15:36:23 | pgp_sym_decrypt() - error 39000: wrong key or corrupt data |