Re: pgsql: Fix failure to check for open() or fsync() failures.

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: pgsql: Fix failure to check for open() or fsync() failures.
Дата
Msg-id 20181227010918.GC2106@paquier.xyz
обсуждение исходный текст
Ответ на Re: pgsql: Fix failure to check for open() or fsync() failures.  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: pgsql: Fix failure to check for open() or fsync() failures.  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On Wed, Dec 26, 2018 at 05:55:36PM -0500, Tom Lane wrote:
> It appears to me that the code is intentionally not worrying about
> fsync failure, so it seems wrong for it to FATAL out if it's unable
> to open the file to fsync it.  And it surely shouldn't do so if the
> file isn't there.

My point is a bit different though: it seems to me that we could just
call BasicOpenFilePerm() and remove the stat() to do exactly the same
things, simplifying the code.
--
Michael

Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: "Tsunakawa, Takayuki"
Дата:
Сообщение: RE: removal of dangling temp tables
Следующее
От: Michael Paquier
Дата:
Сообщение: Re: Offline enabling/disabling of data checksums