From: | Ian Harding <harding(dot)ian(at)gmail(dot)com> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | General PostgreSQL List <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_basebackup ----xlog-method=stream |
Date: | 2017-04-22 01:11:28 |
Message-ID: | 8E472A27-3D2A-42AA-806D-FE648D2CADCB@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> On Apr 21, 2017, at 3:29 PM, Michael Paquier <michael(dot)paquier(at)gmail(dot)com> wrote:
>
>> On Sat, Apr 22, 2017 at 3:02 AM, Ian Harding <harding(dot)ian(at)gmail(dot)com> wrote:
>> Am I misunderstanding how this works? I have WAL archiving set up, so the
>> files are available, but I wanted them included in the backup.
>
> Please note that if you have a WAL archive available, you may not even
> need to have --xlog-method=stream, which is useful to have fully
> safe-contailed backups. For the error regarding the missing WAL
> segment, it could happen if Postgres completes two checkpoints when
> taking the backup. One thing that you could use is a replication slot
> that gives the guarantee that segments are retained. Those have been
> integrated in pg_basebackup with 9.6.
Yeah. I really want to use replication slots but put the server into production without setting the appropriate config settings. I need to schedule some downtime for a restart.
> --
> Michael
From | Date | Subject | |
---|---|---|---|
Next Message | chiru r | 2017-04-22 09:28:10 | pg_basebackup issue |
Previous Message | Cat | 2017-04-22 01:05:46 | Re: Recover PostgreSQL database folder data |