Re: Incorrect errno used with %m for backend code

Поиск
Список
Период
Сортировка
От Ashutosh Sharma
Тема Re: Incorrect errno used with %m for backend code
Дата
Msg-id CAE9k0PmsLE0E3u1D24VZB3C9=Qsj_D_3UmTiNL9ewMSnSpvArw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Incorrect errno used with %m for backend code  (Michael Paquier <michael@paquier.xyz>)
Ответы Re: Incorrect errno used with %m for backend code  (Michael Paquier <michael@paquier.xyz>)
Список pgsql-hackers
On Fri, Jun 22, 2018 at 2:44 PM, Michael Paquier <michael@paquier.xyz> wrote:
> On Fri, Jun 22, 2018 at 01:00:45PM +0530, Ashutosh Sharma wrote:
>> It seems like in case of few system calls for e.g. write system call,
>> errno is not set even if the number of bytes written is smaller than
>> the bytes requested and for such cases we explicitly set an errno to
>> ENOSPC. Something like this,
>>
>>                 /*
>>                  * if write didn't set errno, assume problem is no disk space
>>                  */
>>                 errno = save_errno ? save_errno : ENOSPC;
>>
>> Shouldn't we do similar handling in your patch as well or please let
>> me know if i am missing something here.
>
> Yeah, I can see at least three of them in twophase.c.  Let's fix those
> as well at the same time.

Okay, thanks for the confirmation. Few of them are also there in
origin.c and snapbuild.c files.

-- 
With Regards,
Ashutosh Sharma
EnterpriseDB:http://www.enterprisedb.com


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

Предыдущее
От: Alexander Korotkov
Дата:
Сообщение: Re: [HACKERS] GUC for cleanup indexes threshold.
Следующее
От: Etsuro Fujita
Дата:
Сообщение: Re: Wrong cost estimation for foreign tables join with use_remote_estimatedisabled