From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: fsync error handling in pg_receivewal, pg_recvlogical
Date: Fri, 29 Mar 2019 12:48:09 +0100
Message-ID: <9b49fe44-8f3e-eca9-5914-29e9e99030bf@2ndquadrant.com> (raw)
Do we need to review the fsync error handling in pg_receivewal and
pg_recvlogical, following the recent backend changes? The current
default behavior is that these tools will log fsync errors and then
reconnect and proceed with the next data streaming in. As a result, you
might then have some files in the accumulated WAL that have not been
fsynced. Perhaps a hard exit would be more appropriate?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
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-hackers@postgresql.org
Cc: peter.eisentraut@2ndquadrant.com
Subject: Re: fsync error handling in pg_receivewal, pg_recvlogical
In-Reply-To: <9b49fe44-8f3e-eca9-5914-29e9e99030bf@2ndquadrant.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