Re: [PATCHES] snprintf() argument reordering not working - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: [PATCHES] snprintf() argument reordering not working
Date
Msg-id 4394606D.8050008@dunslane.net
Whole thread Raw
In response to Re: [PATCHES] snprintf() argument reordering not working  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCHES] snprintf() argument reordering not working  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [PATCHES] snprintf() argument reordering not working  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers

Tom Lane wrote:

>Andrew Dunstan <andrew@dunslane.net> writes:
>  
>
>>However, a very simple test shows that the libintl printf does indeed do 
>>%m$ processing:
>>...
>>So the next question is why isn't it working in the build.
>>    
>>
>
>Is it possible that the build that was being complained of was using our
>previous, very-broken snprintf.c?
>
>
>  
>

There's currently a config setting that is supposed to inhibit its use 
on Windows. I am quite confused.

What is more, when I set the locale of my machine to Turkish and run the 
installer project's 8.1_RC1 which I happen to have installed there, and 
set lc_messages to tr_TR.UTF-8, I don't see lines like Nicolai reported:
 LOG:  "$s" veritaban?n transaction ID warp limiti $u

I see this:  LOG:  "2147484146" veritabanin transaction ID warp limiti postgres

So I'm inclined to think there might be something odd about his setup and maybe we aren't quite so broken after all.

cheers

andrew


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Reducing relation locking overhead
Next
From: Tom Lane
Date:
Subject: Re: [PATCHES] snprintf() argument reordering not working