Re: Add %z support to elog/ereport? - Mailing list pgsql-hackers

From Florian Pflug
Subject Re: Add %z support to elog/ereport?
Date
Msg-id 8191B6A5-8EA8-423E-8846-2BFE16850DD8@phlo.org
Whole thread Raw
In response to Re: Add %z support to elog/ereport?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Add %z support to elog/ereport?
List pgsql-hackers
On Jan21, 2014, at 18:56 , Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> Perhaps we should jettison entirely the idea of using the operating
>> system's built-in sprintf and use one of our own that has all of the
>> nice widgets we need, like a format code that's guaranteed to be right
>> for uint64 and one that's guaranteed to be right for Size.  This could
>> turn out to be a bad idea if the best sprintf we can write is much
>> slower than the native sprintf on any common platforms ... and maybe
>> it wouldn't play nice with GCC's desire to check format strings.
> 
> That last is a deal-breaker.  It's not just whether "gcc desires" to check
> this --- we *need* that checking, because people get it wrong without it.

There's an attribute that enables this check for arbitrary functions AFAIR.

best regards,
Florian Pflug




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: proposal: hide application_name from other users
Next
From: Jon Nelson
Date:
Subject: PoC: Duplicate Tuple Elidation during External Sort for DISTINCT