Re: Printing LSN made easy - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Printing LSN made easy
Date
Msg-id 972603.1606669821@sss.pgh.pa.us
Whole thread Raw
In response to Re: Printing LSN made easy  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Printing LSN made easy  (Craig Ringer <craig.ringer@enterprisedb.com>)
Re: Printing LSN made easy  (Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>)
Re: Printing LSN made easy  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
Michael Paquier <michael@paquier.xyz> writes:
> On Fri, Nov 27, 2020 at 04:10:27PM +0530, Ashutosh Bapat wrote:
>> Off list Craig Ringer suggested introducing a new format specifier
>> similar to %m for LSN but I did not get time to take a look at the
>> relevant code. AFAIU it's available only to elog/ereport, so may not
>> be useful generally. But teaching printf variants about the new format
>> would be the best solution. However, I didn't find any way to do that.

> -1.  %m maps to errno, that is much more generic.  A set of macros
> that maps to our internal format would be fine enough IMO.

Agreed.  snprintf.c is meant to implement a recognized standard
(ok, %m is a GNU extension, but it's still pretty standard).
I'm not on board with putting PG-only extensions in there.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: Improving spin-lock implementation on ARM.
Next
From: Heikki Linnakangas
Date:
Subject: Re: Removing unneeded self joins