Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gWMPO-00060n-5A for pgsql-admin@arkaria.postgresql.org; Mon, 10 Dec 2018 14:19:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gWMPL-0003YB-Ee for pgsql-admin@arkaria.postgresql.org; Mon, 10 Dec 2018 14:19:39 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gWMPL-0003Y3-5A for pgsql-admin@lists.postgresql.org; Mon, 10 Dec 2018 14:19:39 +0000 Received: from mail-ot1-x342.google.com ([2607:f8b0:4864:20::342]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gWMPE-0002x0-AE for pgsql-admin@postgresql.org; Mon, 10 Dec 2018 14:19:38 +0000 Received: by mail-ot1-x342.google.com with SMTP id w25so10461943otm.13 for ; Mon, 10 Dec 2018 06:19:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=beaPNIn0xuR63I0hl2LRXWnxC0eYSULWuO+y2nFev68=; b=NX1jdsdvY8UCYA7J561NDSs18W/NRf7SBaGy/BXVftBl2N32MO3hFZ0/OjBbGZagjn VhpWowcKcbJb/HvsIaNOxIP7M0iudxAFJvR5cDPpk9eoD+KUsg0cnRXh4hqegvifVYlH lck1caGbpaW2Jg0AvBgcGQPl1DI0xDeHTpoYmoZaxK2zF+Eqbg74aGI5hYZ+EqXzKwpw tS22Vg29KT2xSlBA7zbj50LiVpyVb/Y10moqV63/6rxpHUTYNETZ6V30jr44ewwWUK1l XmwAQhGj/i8bJjiZyz4vKZvh1ryxZqf8J8W5LXgYpzAJ4jfmCoIlNzKbz+rSkzI45Qjy 14dA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=beaPNIn0xuR63I0hl2LRXWnxC0eYSULWuO+y2nFev68=; b=ZQ8hzBV4St5vsRPiUb1jXDa2O8J/rurQuRrOz5SXNZmOf4Mefy6xTw+f78LMpYZl17 NocwiRfuDABaZDE2fg0ghcxYThHwdB1GA7HDfZGhZjV0+22vEe+JBIfOfzVBOVDCLXEc u9MSjkeca7uuJWzPhNsa6XfW7lMcJ43ofR3o449tzTKi9mCod30LL5wqfRL0c2sGeb3j NQiHz/YjYNQebtdRfL4cJNp4XQJfZWBpOoUWo4/pbc8lJcfWDLRcoyReqkFJTjYg2+Ve 5djktlSd08a0phL1GJrNgr0CixHMK2rEI+1JHMPpiaN9P4KLD926vtkth57siVvLgAfx aKRA== X-Gm-Message-State: AA+aEWZdo8xvYzzhPK1XKT3TPfJtaBc4E5jXahSrzcOQf6nsuj/+KMn+ Sg10ch0JHEVHzziqvzJgKuk1slef X-Google-Smtp-Source: AFSGD/XTMru8uNjyneXBOGFdL2W6nIDcmTKAhxy86UyZZitDK6/qUDJcQY/mbL9Sw4R/57WlhBWtjA== X-Received: by 2002:a9d:5e8c:: with SMTP id f12mr9257414otl.343.1544451569665; Mon, 10 Dec 2018 06:19:29 -0800 (PST) Received: from [192.168.1.10] (ip70-171-116-89.no.no.cox.net. [70.171.116.89]) by smtp.googlemail.com with ESMTPSA id q128sm5328107oia.4.2018.12.10.06.19.28 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 10 Dec 2018 06:19:28 -0800 (PST) Subject: Re: pgbackrest periodic WAL backups? To: pgsql-admin@postgresql.org References: <20181209191035.GG3415@tamriel.snowman.net> <859f2c25-3a22-71fa-e1fa-764724183764@gmail.com> From: Ron Message-ID: <1faf5f2b-b023-091c-c1a5-8646cbbc8999@gmail.com> Date: Mon, 10 Dec 2018 08:19:27 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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.