Re: Add pg_file_sync() to adminpack
От | Fujii Masao |
---|---|
Тема | Re: Add pg_file_sync() to adminpack |
Дата | |
Msg-id | c5b0837a-8eed-73d4-0ebc-af970c4f66e7@oss.nttdata.com обсуждение исходный текст |
Ответ на | Re: Add pg_file_sync() to adminpack (Michael Paquier <michael@paquier.xyz>) |
Ответы |
Re: Add pg_file_sync() to adminpack
|
Список | pgsql-hackers |
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
Вложения
В списке pgsql-hackers по дате отправления: