> Uh, no. You can pretty much assume that LATIN1 will take any random > byte string; likewise for any other single-byte encoding. UTF8 as a > default is a bit safer because it's significantly more likely that it > will be able to detect non-UTF8 input. > > regards, tom lane >
So, IIUC, the general approach is: *Leave the default client_encoding = server_encoding (in this case UTF8) *Rely on the client to change client_encoding on a session basis only Thanks, --Lee -- Lee Hachadoorian PhD Student, Geography Program in Earth & Environmental Sciences CUNY Graduate Center -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
