Re: Why are wait events not reported even though it reads/writes atimeline history file?

Поиск
Список
Период
Сортировка
От Fujii Masao
Тема Re: Why are wait events not reported even though it reads/writes atimeline history file?
Дата
Msg-id f0a38d7d-1e81-7a08-abf8-61b8d4481c91@oss.nttdata.com
обсуждение исходный текст
Ответ на Re: Why are wait events not reported even though it reads/writes atimeline history file?  (Michael Paquier <michael@paquier.xyz>)
Ответы Re: Why are wait events not reported even though it reads/writes atimeline history file?  (Michael Paquier <michael@paquier.xyz>)
Список pgsql-hackers

On 2020/05/02 11:24, Michael Paquier wrote:
> On Fri, May 01, 2020 at 12:04:56PM +0900, Fujii Masao wrote:
>> I applied cosmetic changes to the patch (attached). Barring any objection,
>> I will push this patch (also back-patch to v10 where wait-event for timeline
>> file was added).
> 
> Sorry for arriving late to the party.  I have one tiny comment.
> 
>> +        pgstat_report_wait_start(WAIT_EVENT_TIMELINE_HISTORY_READ);
>> +        res = fgets(fline, sizeof(fline), fd);
>> +        pgstat_report_wait_end();
>> +        if (ferror(fd))
>> +            ereport(ERROR,
>> +                    (errcode_for_file_access(),
>> +                     errmsg("could not read file \"%s\": %m", path)));
>> +        if (res == NULL)
>> +            break;
> 
> It seems to me that there is no point to check ferror() if fgets()
> does not return NULL, no?

Yeah, so I updated the patch so that ferror() is called only
when fgets() returns NULL. Attached is the updated version of
the patch.

Regards,

-- 
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION

Вложения

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

Предыдущее
От: Masahiko Sawada
Дата:
Сообщение: Re: xid wraparound danger due to INDEX_CLEANUP false
Следующее
От: Fujii Masao
Дата:
Сообщение: Re: Should smgrdounlink() be removed?