Re: Add pg_file_sync() to adminpack
Fujii Masao <masao.fujii@oss.nttdata.com>
From: Fujii Masao <masao.fujii@oss.nttdata.com>
To: Michael Paquier <michael@paquier.xyz>, Robert Haas <robertmhaas@gmail.com>
Cc: Atsushi Torikoshi <atorik@gmail.com>, Fujii Masao
<masao.fujii@gmail.com>, Julien Rouhaud <rjuju123@gmail.com>,
Arthur Zakirov <zaartur@gmail.com>,
PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2020-01-17T07:05:03Z
Lists: pgsql-hackers
Attachments
- pg_file_sync_v4.patch (text/plain) patch v4
On 2020/01/17 13:36, Michael Paquier wrote: > On Thu, Jan 16, 2020 at 09:51:24AM -0500, Robert Haas wrote: >> On Tue, Jan 14, 2020 at 10:08 AM Atsushi Torikoshi <atorik@gmail.com> wrote: >>> fails we can get error messages. So it seems straightforward for me to >>> 'return true on success and emit an ERROR otherwise'. >> >> I agree with reporting errors using ERROR, but it seems to me that we >> ought to then make the function return 'void' rather than 'bool'. > > Yeah, that should be either ERROR and return a void result, or issue a > WARNING/ERROR (depending on the code path, maybe PANIC?) with a > boolean status returned if there is a WARNING. Mixing both concepts > with an ERROR all the time and always a true status is just weird, > because you know that if no errors are raised then the status will be > always true. So there is no point to have a boolean status to begin > with. OK, so our consensus is to return void on success and throw an error otherwise. Attached is the updated version of the patch. Regards, -- Fujii Masao NTT DATA CORPORATION Advanced Platform Technology Group Research and Development Headquarters
Commits
-
Add pg_file_sync() to adminpack extension.
- d694e0bb793e 13.0 landed