[DBD::Pg] Quick notes about preferred client_encoding

[dbdpg-commits]

Committed by Greg Sabino Mullane <g...@endpoint.com>

Quick notes about preferred client_encoding

---
 Pg.pm | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/Pg.pm b/Pg.pm
index e8f68c7..b48108a 100644
--- a/Pg.pm
+++ b/Pg.pm
@@ -1601,7 +1601,7 @@ use 5.008001;
                return 1;
        } ## end bind_param_array
 
-       sub private_attribute_info {
+       sub private_attribute_info {
                return {
                                pg_async                  => undef,
                                pg_bound                  => undef,
@@ -3791,6 +3791,16 @@ Not used by DBD::Pg. See the note about L</Cursors> 
elsewhere in this document.
 
 =head1 FURTHER INFORMATION
 
+=head2 Encoding
+
+DBD::Pg has extensive support for a client_encoding of UTF-8, and most 
+things like encoding and decoding should happen automatically. If you are 
+using a different encoding, you may need do the encoding and decoding 
+yourself. For this reason, it is highly recommended to always use a 
+client_encoding of UTF-8. The server_encoding can be anything, and no 
+recommendations are made there, other than avoid SQL_ASCII whenever 
+possible.
+
 =head2 Transactions
 
 Transaction behavior is controlled via the L</AutoCommit> attribute. For a
-- 
1.8.4