Re: [pgsql-hackers-win32] snprintf causes regression - Mailing list pgsql-hackers

From pgsql@mohawksoft.com
Subject Re: [pgsql-hackers-win32] snprintf causes regression
Date
Msg-id 16512.24.91.171.78.1110504589.squirrel@mail.mohawksoft.com
Whole thread Raw
In response to Re: [pgsql-hackers-win32] snprintf causes regression tests  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: [pgsql-hackers-win32] snprintf causes regression tests  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [pgsql-hackers-win32] snprintf causes regression  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
> Tom Lane wrote:
>> Bruce Momjian <pgman@candle.pha.pa.us> writes:
>> > Please see my posting about using a macro for snprintf.  If the
>> current
>> > implementation of snprintf is enough for our existing translation
>> users
>> > we probably don't need to add anything more to it because snprintf
>> will
>> > not be exported to client applications.
>>
>> The CVS-tip implementation is fundamentally broken and won't work even
>> for our internal uses.  I've not wasted time complaining about it
>> because I thought we were going to replace it.  If we can't find a
>> usable replacement then we're going to have to put a lot of effort
>> into fixing what's there.  On the whole I think the effort would be
>> better spent importing someone else's solution.
>
> Oh, so our existing implementation doesn't even meet our needs. OK.

Wasn't the issue about odd behavior of the Win32 linker choosing the wrong
vnsprintf?

pgsql-hackers by date:

Previous
From: Christopher Kings-Lynne
Date:
Subject: Re: Raw size
Next
From: Kevin Brown
Date:
Subject: Re: fool-toleranced optimizer