Skip site navigation (1) Skip section navigation (2)

Re: BUG #4186: set lc_messages does not work

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Thomas H" <me(at)alternize(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4186: set lc_messages does not work
Date: 2008-05-25 22:50:32
Message-ID: 4374.1211755832@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackers
"Thomas H" <me(at)alternize(dot)com> writes:
> Bug reference:      4186
> Logged by:          Thomas H
> Email address:      me(at)alternize(dot)com
> PostgreSQL version: 8.3.1
> Operating system:   Windows 2003
> Description:        set lc_messages does not work
> Details: 

> the patch discussed here [1] that supposedly made the win32 msvc builds use
> lc_locale properly has flaws.

I think a large part of the confusion that's been evidenced in this
thread is because you are submitting a "bug report" about a patch that is
not in fact in 8.3.1 (and is unlikely ever to appear in 8.3.x at all).
It's unclear what you are really testing: stock 8.3.1?  8.3.1 plus that
patch?  CVS HEAD plus the patch?

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2008-05-25 23:07:00
Subject: Re: plpgsql: penalty due to double evaluation of parameters
Previous:From: Greg Sabino MullaneDate: 2008-05-25 21:19:46
Subject: Re: \df displaying volatility

pgsql-bugs by date

Next:From: Tom LaneDate: 2008-05-25 22:53:56
Subject: Re: error message "psql: expected authentication request from server, but received " when using psql to connect remote database
Previous:From: Dennis GilmoreDate: 2008-05-24 05:51:27
Subject: Re: BUG #4190: sparc64 test suite fails

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group