2009/10/23 Alvaro Herrera <alvhe...@commandprompt.com>: > Peter Eisentraut wrote: > >> Note that only glibc supports switching the language at run time. And >> doing it is probably very expensive if you want to do it twice per >> message. > > Ouch :-( > >> I think you could probably get much of the use case out of this if you >> concentrate on making two switches for the client and the log, which can >> be set to a language or "untranslated", and if you choose a language it >> has to be the same for both. > > So we'd go with a single setting to define language, which would be the > current lc_messages, and two new settings, say translate_log_messages > and translate_client_messages, the latter being USERSET. > > Does that sound reasonable?
Does to me. It would certainly cover my use-case, which is that unless your logs are in english, it's really hard to google on anything :-) (I guess it may work for the "big" languages like spanish, french and german, but that's about it. And even then, you're missing out on a lot of resources) -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/ -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
