Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id SAA47758 for ; Fri, 24 Sep 1999 18:37:38 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id SAA07117; Fri, 24 Sep 1999 18:36:25 -0400 (EDT) To: Bishop cc: pgsql-interfaces@hub.org Subject: Re: [INTERFACES] NOTICE: Unrecognized variable client_encoding In-reply-to: Your message of Fri, 24 Sep 1999 18:46:42 +0200 <37EBAAF2.1E1B7255@jrc.it> Date: Fri, 24 Sep 1999 18:36:25 -0400 Message-ID: <7115.938212585@sss.pgh.pa.us> From: Tom Lane Bishop writes: > to be reliable. Since compiling PostgreSQL 6.5.2 I have seen "NOTICE: > unrecognized variable client_encoding" messages, although data do not > appear to be getting lost or corrupted. Is this message important, or > can I safely ignore it? Evidently you compiled the server without the MULTIBYTE option, but are invoking it with a client whose libpq was compiled with the option. libpq is trying to tell the server what multibyte character set it wants to use, and the server is responding that it hasn't got that feature. If you aren't worried about non-US-ASCII characters then leaving MULTIBYTE off is good; otherwise you may want to rebuild with it on. In any case, to get rid of the notice you'd need to build the client library with the same options as the server. regards, tom lane