Hi,
Thanks very much Daniel ! :))
You hit the problem.
lc_messages were configured with 'French_France.1252' (as usual)
Setting it to 'C' resolve the issue.
Another way is to set client_min_messages to 'error'
So, it seems that a 32 bits PG 9.4.4 return to client the UTF8 error
generated
On 07/08/2015 01:04 AM, Thierry Hauchard wrote:
Hy,
We can't upgrade our customers from 8.4 to 9.4.4 if they have a 32 bits
server machine (Windows 2008, 2007...).
There is no problem with PG 64 bits.
Except below you say only for majority of 64bit machines, so are the
problems when they
There is NO problem on 64 bits machines with PG 64 bits.
(We have not try PG 32 bits on 64 bits machine.)
There IS problem on all 32 bits machine with PG 32 bits
All databases are encoded on PG in UTF8
We set that on all connexions :
SET CLIENT_ENCODING TO WIN1252;
SET bytea_output TO escape;
On 07/08/2015 08:40 AM, Thierry Hauchard wrote:
There is NO problem on 64 bits machines with PG 64 bits.
I saw this line from your previous post:
No issue on 64bits machine (majority of our customers).
Realize now that this means the majority of your customers are using
64bit Windows. I
Hy,
We can't upgrade our customers from 8.4 to 9.4.4 if they have a 32 bits
server machine (Windows 2008, 2007...).
There is no problem with PG 64 bits.
When restoring from backup (created from 8.4 database with PG_Dump
9.4.4), the log shows errors about UTF like :
2015-07-07 17:03:35 CEST
Thierry Hauchard wrote:
When restoring from backup (created from 8.4 database with PG_Dump
9.4.4), the log shows errors about UTF like :
2015-07-07 17:03:35 CEST ERREUR: séquence d'octets invalide pour
l'encodage « UTF8 » : 0xf4 0x6c 0x65 0x20
[...]
UPDATE test_table SET str_field
On 07/08/2015 08:40 AM, Thierry Hauchard wrote:
There is NO problem on 64 bits machines with PG 64 bits.
(We have not try PG 32 bits on 64 bits machine.)
There IS problem on all 32 bits machine with PG 32 bits
Further thought, are the 32bit and 64bit Windows in the same version of
Windows or
Thierry,
Please post the output of
$ psql -l
for the database in question for both the 32-bit and 64-bit servers. That will
show what encoding was specified when the databases where created.
Also, post the output of
$ psql dbname here login -c “show client_encoding”
$ psql dbname here
Hi,
which build of PosgreSQL did you use?
Postgres Professional has published today its Windows PostgreSQL installer for
9.4.4, which solves some strange issues with russian encoding in psql occurring
in the EDB build.
I'm not sure it can help in your case.
The installer is at
