Re: convert elog(LOG) calls to ereport

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: convert elog(LOG) calls to ereport
Date: 2020-12-04 13:34:26
Message-ID: 41f5c5f7-3611-9bdc-cfad-9f61146419ff@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2020-12-02 15:04, Alvaro Herrera wrote:
>> - elog(LOG, "WSAIoctl(SIO_KEEPALIVE_VALS) failed: %ui",
>> - WSAGetLastError());
>> + ereport(LOG,
>> + (errmsg("WSAIoctl(SIO_KEEPALIVE_VALS) failed: %ui",
>> + WSAGetLastError())));
>
> Please take the opportunity to move the flag name out of the message in
> this one, also.

done

> I do wonder if it'd be a good idea to move the syscall
> name itself out of the message, too; that would reduce the number of
> messages to translate 50x to just "%s(%s) failed: %m" instead of one
> message per distinct syscall.

Seems useful, but perhaps as a separate project.

> Should fd.c messages do errcode_for_file_access() like elsewhere?

yes, done

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2020-12-04 13:34:57 Re: convert elog(LOG) calls to ereport
Previous Message Dilip Kumar 2020-12-04 12:16:34 Re: [HACKERS] Custom compression methods