| From: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: invalid byte sequence ? |
| Date: | 2006-08-24 21:22:26 |
| Message-ID: | 20060824212226.GF6550@merkur.hilbert.loc |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Thu, Aug 24, 2006 at 01:17:49PM -0400, Tom Lane wrote:
> I guess the key point might be "what do we do if the client locale
> is C?" Perhaps if it's C, we continue to use the server encoding
> as we have in the past. This would be a reasonable fallback in
> other cases where we fail to deduce an encoding from the locale, too.
In that case I would suggest to also emit a suitable warning
(with a postgresql.conf option to switch that off which
defaults to ON).
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Randy How | 2006-08-25 01:07:14 | FW: Serverlog 100GB |
| Previous Message | Frank Cohen | 2006-08-24 20:56:12 | Re: XPath and XML support |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeremy Kronuz | 2006-08-24 23:42:51 | Re: ISBN/ISSN/ISMN/EAN13 module |
| Previous Message | Bernd Helmle | 2006-08-24 20:25:46 | Re: Updatable views |