From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mariel Cherkassky <mariel.cherkassky@gmail.com>
cc: pgpool-general <pgpool-general@pgpool.net>,
        pgsql-admin@lists.postgresql.org
Subject: Re: invalid value for parameter "client_encoding": "ISO_8859_8"
In-reply-to: 
 <CA+t6e1k4c=GkFukoNFxdeoZY6KwLMxmz_Qu22E9uzxUNHzqZ4Q@mail.gmail.com>
References: 
 <CA+t6e1k4c=GkFukoNFxdeoZY6KwLMxmz_Qu22E9uzxUNHzqZ4Q@mail.gmail.com>
Comments: In-reply-to Mariel Cherkassky <mariel.cherkassky@gmail.com>
	message dated "Sun, 01 Jul 2018 10:29:11 +0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <62157.1530459196.1@sss.pgh.pa.us>
Date: Sun, 01 Jul 2018 11:33:16 -0400
Message-ID: <62158.1530459196@sss.pgh.pa.us>
Precedence: bulk

Mariel Cherkassky <mariel.cherkassky@gmail.com> writes:
> My postgresql env consist of 3 nodes(9.6 version) and 2 pgpool`s that acts
> as a load balancer. I'm using postgresql as a database for the next apps :
> bitbucket,jira and crowd. However, I'm getting alot of errors in the pgpool
> log about the client_encoding for every connection that comes from one of
> those application :

> invalid value for parameter "client_encoding": "ISO_8859_8"
> Cannot change "client_encoding" now.

[ digs around ... ] The "Cannot change" bit seems to indicate that this
error is coming from check_client_encoding(), and it's failing because
it cannot change client_encoding for an existing session outside a
transaction.  The comment about it is:

     * ... This would only happen if someone tries to change
     * client_encoding in postgresql.conf and then SIGHUP existing sessions.
     * It seems like a bad idea for client_encoding to change that way anyhow,
     * so we don't go out of our way to support it.

I'm not very sure how you'd get into a state where this was affecting
new sessions as well as pre-existing ones, or why it would affect only
some sessions.  Maybe the latter could be explained if all but this one
app explicitly set client_encoding for themselves.

Anyway, I think it's impossible for the client app to trigger this
by itself.  There must be some server-side source of this value,
if not postgresql.conf then maybe ALTER DATABASE/ROLE SET?

			regards, tom lane