From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-admin@postgresql.org
Subject: Re: pgbackrest periodic WAL backups?
Date: Mon, 10 Dec 2018 08:19:27 -0600
Message-ID: <1faf5f2b-b023-091c-c1a5-8646cbbc8999@gmail.com> (raw)
In-Reply-To: <fb4b6715-42db-958c-b79f-fe507f52b4d7@pgmasters.net>
References: <df843a29-494a-7e72-e95a-647941979f1a@gmail.com>
<20181209191035.GG3415@tamriel.snowman.net>
<859f2c25-3a22-71fa-e1fa-764724183764@gmail.com>
<fb4b6715-42db-958c-b79f-fe507f52b4d7@pgmasters.net>
On 12/10/2018 07:37 AM, David Steele wrote:
> On 12/9/18 5:24 PM, Ron wrote:
>> On 12/09/2018 01:10 PM, Stephen Frost wrote:
>>> You can address that risk by enabling archive_timeout, which will make
>>> PostgreSQL archive the WAL file even if it isn't full after a certain
>>> amount of time, reducing the potential data loss window.
>> I thought checkpoint_timeout forced a WAL switch.
> Checkpoints do not automatically switch WAL. archive_timeout is the way
> to go.
Thanks for the clarification.
--
Angular momentum makes the world go 'round.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: ronljohnsonjr@gmail.com
Subject: Re: pgbackrest periodic WAL backups?
In-Reply-To: <1faf5f2b-b023-091c-c1a5-8646cbbc8999@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox