Postgres Pro
Downloads
Home   >   mailing lists

Re: client-side fsync() error handling - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: client-side fsync() error handling
Date
Msg-id 0412a2fb-cbde-08c6-9ff2-cfab5c27a3b8@2ndquadrant.com
Whole thread Raw
In response to Re: client-side fsync() error handling  (Michael Paquier <michael@paquier.xyz>)
Responses Re: client-side fsync() error handling
List pgsql-hackers
Tree view 
On 2020-02-12 06:28, Michael Paquier wrote:
> Now, don't we need to care about durable_rename() and make the
> panic-like failure an optional choice?  From what I can see, this
> routine is used now in the backend for pg_basebackup to rename
> temporary history files or partial WAL segments.

durable_rename() calls fsync_fname(), so it would be covered by this 
change.  The other file access calls in there can be handled by normal 
error handling, I think.  Is there any specific scenario you have in mind?

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: backend type in log_line_prefix?
Next
From: Peter Eisentraut
Date:
Subject: Re: Exposure related to GUC value of ssl_passphrase_command