Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 5db0ef8

Browse files
committed
Add explanation about 'Unrecognized variable client_encoding'
message at startup.
1 parent 321eedd commit 5db0ef8

File tree

1 file changed

+13
-1
lines changed

1 file changed

+13
-1
lines changed

doc/src/sgml/trouble.sgml

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/Attic/trouble.sgml,v 2.5 2000/03/31 03:27:41 thomas Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/Attic/trouble.sgml,v 2.6 2000/04/08 23:32:34 tgl Exp $
33
-->
44

55
<Chapter Id="trouble">
@@ -137,6 +137,18 @@ FATAL 1: Database testdb does not exist in pg_database
137137
Postgres username, which may or may not be the right thing.
138138
</para>
139139

140+
<para>
141+
<ProgramListing>
142+
NOTICE: Unrecognized variable client_encoding
143+
</ProgramListing>
144+
This isn't an error; in fact, it's quite harmless. You'll see this
145+
message at startup if you use a client compiled with MULTIBYTE support
146+
to connect to a server compiled without it. (The client is trying
147+
to tell the server what character set encoding it wants, but the
148+
server has no idea what it's talking about.) If the message bothers
149+
you, use a client compiled with the same options as the server.
150+
</para>
151+
140152
</sect1>
141153

142154
<sect1>

0 commit comments

Comments
 (0)