Thanks Andrew. I will test the next release.
Martin
-Original Message-
From: Andrew Dunstan [mailto:and...@dunslane.net]
Sent: 08 June 2013 16:43
To: Tom Lane
Cc: Heikki Linnakangas; k...@rice.edu; Martin Schäfer; pgsql-
hack...@postgresql.org
Subject: Re: [HACKERS] UTF-8 encoding
Can't really blame Windows on that. On Windows, we don't require that the
encoding and LC_CTYPE's charset match. The OP used UTF-8 encoding in the
server, but LC_CTYPE=English_United Kingdom.1252, ie. LC_CTYPE implies
WIN1252 encoding. We allow that and it generally works on Windows
because
I try to create database columns with umlauts, using the UTF8 client encoding.
However, the server seems to mess up the column names. In particular, it seems
to perform a lowercase operation on each byte of the UTF-8 multi-byte sequence.
Here is my code:
const wchar_t *strName = Lid_äß;
-Original Message-
From: k...@rice.edu [mailto:k...@rice.edu]
Sent: 03 June 2013 16:48
To: Martin Schäfer
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] UTF-8 encoding problem w/ libpq
On Mon, Jun 03, 2013 at 03:40:14PM +0100, Martin Schäfer wrote:
I try to create
Okay. I'll go fix the core code, and you can take out
whatever you want in GiST/GIN.
Which PostgreSQL versions will contain the fix?
Regards,
Martin Schaefer
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
