Re: Some code cleanup for pgbench and pg_verifybackup - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Some code cleanup for pgbench and pg_verifybackup
Date
Msg-id YQJV6x4XbEluEuzQ@paquier.xyz
Whole thread Raw
In response to Re: Some code cleanup for pgbench and pg_verifybackup  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Wed, Jul 28, 2021 at 10:28:13AM -0400, Robert Haas wrote:
> I think all of these are reasonable fixes. In the case of
> pg_basebackup, a chmod() failure doesn't necessarily oblige us to give
> up and exit; we could presumably still write the data. But it may be
> best to give up and exit. The other cases appear to be clear bugs.

Yeah, there are advantages in both positions, still it is more natural
to me to not ignore this kind of failures.  Note the inconsistency
with initdb for example.  So, done.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Peter Smith
Date:
Subject: Re: Out-of-memory error reports in libpq
Next
From: Kyotaro Horiguchi
Date:
Subject: Re: Use WaitLatch for {pre, post}_auth_delay instead of pg_usleep