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

Commit d6d9653

Browse files
committed
Remove docs that say psql \encoding doesn't track SET client_encoding.
1 parent 17bb563 commit d6d9653

File tree

1 file changed

+1
-8
lines changed

1 file changed

+1
-8
lines changed

doc/src/sgml/ref/psql-ref.sgml

+1-8
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.93 2003/07/28 00:14:42 tgl Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.94 2003/08/02 02:44:38 momjian Exp $
33
PostgreSQL documentation
44
-->
55

@@ -1070,13 +1070,6 @@ Tue Oct 26 21:40:57 CEST 1999
10701070
Sets the client character set encoding. Without an argument, this command
10711071
shows the current encoding.
10721072
</para>
1073-
<note>
1074-
<para>
1075-
This command will not notice changes made directly by <command>SET
1076-
client_encoding</>. If you use <command>\encoding</command>,
1077-
be sure to use it to set as well as examine the encoding.
1078-
</para>
1079-
</note>
10801073
</listitem>
10811074
</varlistentry>
10821075

0 commit comments

Comments
 (0)