| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Mariel Cherkassky <mariel(dot)cherkassky(at)gmail(dot)com> |
| 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:34:04 |
| Message-ID: | 19162.1531319644@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mariel Cherkassky | 2018-07-11 14:37:00 | Re: invalid value for parameter "client_encoding": "ISO_8859_8" |
| Previous Message | Mariel Cherkassky | 2018-07-11 14:19:43 | Re: invalid value for parameter "client_encoding": "ISO_8859_8" |