Re: invalid value for parameter "client_encoding": "ISO_8859_8"

From: Mariel Cherkassky <mariel(dot)cherkassky(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: invalid value for parameter "client_encoding": "ISO_8859_8"
Date: 2018-07-11 14:37:00
Message-ID: CA+t6e1kyLBUL+2-xwEj5r7F7EAmvadobWCbk3-X38p2NHSk=bg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)sss(dot)pgh(dot)pa(dot)us>:

> Mariel Cherkassky <mariel(dot)cherkassky(at)gmail(dot)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
>

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Mariel Cherkassky 2018-07-11 14:38:01 upgrading postgresql cluster(3 nodes) to v10 without DOWNTIME
Previous Message Tom Lane 2018-07-11 14:34:04 Re: invalid value for parameter "client_encoding": "ISO_8859_8"