| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, Alejandro Forero Cuervo <bachue(at)bachue(dot)com>, pgsql-general(at)postgresql(dot)org, boti(at)nimonic(dot)com |
| Subject: | Re: Getting error codes for failed queries? |
| Date: | 2003-10-16 03:51:51 |
| Message-ID: | 16022.1066276311@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> The other problem is that changing the language at runtime doesn't really
> work well, because there are obscure dependencies on LC_CTYPE and
> depending on the implementation of gettext there is some caching going on.
> So the real answer is actually, "It doesn't work, but the superuser is
> free to try."
Ugh. But LC_CTYPE isn't really going anywhere in our current setup, and
the feature would still be useful if we forced users to select their
message language at backend start time (via PGOPTIONS, for instance).
Can we get anywhere if we make those assumptions?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruno BAGUETTE | 2003-10-16 06:37:15 | Lost views in a PostgreSQL 7.1. dump file ? |
| Previous Message | Dennis Gearon | 2003-10-16 03:16:10 | Re: Porting Code to Postgresql |