Re: invalid value for parameter "client_encoding": "ISO_8859_8" - Mailing list pgsql-admin

From Mariel Cherkassky
Subject Re: invalid value for parameter "client_encoding": "ISO_8859_8"
Date
Msg-id CA+t6e1kyLBUL+2-xwEj5r7F7EAmvadobWCbk3-X38p2NHSk=bg@mail.gmail.com
Whole thread Raw
In response to Re: invalid value for parameter "client_encoding": "ISO_8859_8"  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: invalid value for parameter "client_encoding": "ISO_8859_8"  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: invalid value for parameter "client_encoding": "ISO_8859_8"  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin
Yes indeed.
postgres=# show config_file;
             config_file              
--------------------------------------
 /PostgreSQL/9.6/data/postgresql.conf

and I opened this file.. What would you suggest to look in the conf file ? The only thing that i thought about is the next parameter : 
#client_encoding = ISO_8859_8

but its default..
So what next ?

2018-07-11 17:34 GMT+03:00 Tom Lane <tgl@sss.pgh.pa.us>:
Mariel Cherkassky <mariel.cherkassky@gmail.com> writes:
> I realized that it happens immediatly when I reload my cluster settings via
> pg_ctl reload. Immediatly raised the curremt message for every database in
> my cluster :
> 2018-07-11 17:17:56 IDTjiradbuserjiradbERROR:  invalid value for parameter
> "client_encoding": "ISO_8859_8"
> 2018-07-11 17:17:56 IDTjiradbuserjiradbDETAIL:  Cannot change
> "client_encoding" now.

That's exactly what I'd expect if the setting were coming from
postgresql.conf, so I think you need to look harder.  Are you sure
you are looking at the right copy of postgresql.conf (check "show
config_file" to be sure)?  Maybe it's in some file included by
postgresql.conf?  What about postgresql.auto.conf?

                        regards, tom lane

pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: invalid value for parameter "client_encoding": "ISO_8859_8"
Next
From: Mariel Cherkassky
Date:
Subject: upgrading postgresql cluster(3 nodes) to v10 without DOWNTIME