<div dir="rtl"><div style="" dir="ltr">It happens to all the sessions I have to all the databases. In other words, different apps are connected to different databases but I still keep getting those errors. I queried pg_shadow and I didnt see that a specific user has a different client_encoding configured. Moreover, the client_encoding is set to default in postgresql.conf.</div><div style="" dir="ltr"><br></div><div style="" dir="ltr">What else can I check ? I'm trying to check the if the problem is in the pool as tatsuo suggested but is there anything else that I can check ?</div></div><div class="gmail_extra"><br><div class="gmail_quote"><div dir="ltr">2018-07-01 18:33 GMT+03:00 Tom Lane <span dir="ltr"><<a href="mailto:tgl@sss.pgh.pa.us" target="_blank">tgl@sss.pgh.pa.us</a>></span>:</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">Mariel Cherkassky <<a href="mailto:mariel.cherkassky@gmail.com">mariel.cherkassky@gmail.com</a>> writes:<br>
> My postgresql env consist of 3 nodes(9.6 version) and 2 pgpool`s that acts<br>
> as a load balancer. I'm using postgresql as a database for the next apps :<br>
> bitbucket,jira and crowd. However, I'm getting alot of errors in the pgpool<br>
> log about the client_encoding for every connection that comes from one of<br>
> those application :<br>
<br>
> invalid value for parameter "client_encoding": "ISO_8859_8"<br>
> Cannot change "client_encoding" now.<br>
<br>
</span>[ digs around ... ] The "Cannot change" bit seems to indicate that this<br>
error is coming from check_client_encoding(), and it's failing because<br>
it cannot change client_encoding for an existing session outside a<br>
transaction. The comment about it is:<br>
<br>
* ... This would only happen if someone tries to change<br>
* client_encoding in postgresql.conf and then SIGHUP existing sessions.<br>
* It seems like a bad idea for client_encoding to change that way anyhow,<br>
* so we don't go out of our way to support it.<br>
<br>
I'm not very sure how you'd get into a state where this was affecting<br>
new sessions as well as pre-existing ones, or why it would affect only<br>
some sessions. Maybe the latter could be explained if all but this one<br>
app explicitly set client_encoding for themselves.<br>
<br>
Anyway, I think it's impossible for the client app to trigger this<br>
by itself. There must be some server-side source of this value,<br>
if not postgresql.conf then maybe ALTER DATABASE/ROLE SET?<br>
<br>
regards, tom lane<br>
</blockquote></div><br></div>