Re: Add pg_file_sync() to adminpack - Mailing list pgsql-hackers

From Arthur Zakirov
Subject Re: Add pg_file_sync() to adminpack
Date
Msg-id 57122c73-7461-183b-2405-a5c2d0bf197e@gmail.com
Whole thread Raw
In response to Re: Add pg_file_sync() to adminpack  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Add pg_file_sync() to adminpack  (Fujii Masao <masao.fujii@oss.nttdata.com>)
List pgsql-hackers
On 2020/01/24 14:56, Michael Paquier wrote:
> On Fri, Jan 24, 2020 at 01:28:29PM +0900, Arthur Zakirov wrote:
>> It is compiled and passes the tests. There is the documentation and it is
>> built too without an error.
>>
>> It seems that consensus about the returned type was reached and I marked the
>> patch as "Ready for Commiter".
> 
> +       fsync_fname_ext(filename, S_ISDIR(fst.st_mode), false, ERROR);
> One comment here: should we warn better users in the docs that a fsync
> failule will not trigger a PANIC here?  Here, fsync failure on heap
> file => ERROR => potential data corruption.

Ah, true. It is possible to add couple sentences that pg_file_sync() 
doesn't depend on data_sync_retry GUC and doesn't raise a PANIC even for 
database files.

-- 
Arthur



pgsql-hackers by date:

Previous
From: Julien Rouhaud
Date:
Subject: Re: Add pg_file_sync() to adminpack
Next
From: Mike Lissner
Date:
Subject: Patching documentation of ALTER TABLE re column type changes onbinary-coercible fields