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

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: pgsql: Fix failure to check for open() or fsync() failures.
Дата
Msg-id 32282.1545874522@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: pgsql: Fix failure to check for open() or fsync() failures.  (Michael Paquier <michael@paquier.xyz>)
Ответы Re: pgsql: Fix failure to check for open() or fsync() failures.  (Michael Paquier <michael@paquier.xyz>)
Список pgsql-hackers
Michael Paquier <michael@paquier.xyz> writes:
> 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.

Oh, I see.  Yeah, if we're ignoring errors anyway, the stat calls
seem redundant.

            regards, tom lane


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

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: random() (was Re: New GUC to sample log queries)
Следующее
От: Tom Lane
Дата:
Сообщение: Re: random() (was Re: New GUC to sample log queries)