Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fdGC9-0000mA-3F for pgsql-admin@arkaria.postgresql.org; Wed, 11 Jul 2018 14:34:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fdGC7-0008KF-1R for pgsql-admin@arkaria.postgresql.org; Wed, 11 Jul 2018 14:34:15 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fdGC6-0008K7-Qb for pgsql-admin@lists.postgresql.org; Wed, 11 Jul 2018 14:34:14 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fdGBz-0007Iv-Mz for pgsql-admin@lists.postgresql.org; Wed, 11 Jul 2018 14:34:14 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id w6BEY4B6019163; Wed, 11 Jul 2018 10:34:04 -0400 From: Tom Lane To: Mariel Cherkassky cc: pgsql-admin@lists.postgresql.org Subject: Re: invalid value for parameter "client_encoding": "ISO_8859_8" In-reply-to: References: <62158.1530459196@sss.pgh.pa.us> Comments: In-reply-to Mariel Cherkassky message dated "Wed, 11 Jul 2018 17:19:43 +0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <19161.1531319644.1@sss.pgh.pa.us> Date: Wed, 11 Jul 2018 10:34:04 -0400 Message-ID: <19162.1531319644@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Mariel Cherkassky 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