Andrew Sullivan <ajs@xxxxxxxxxxxxxxx> writes: > On Mon, Oct 10, 2005 at 10:27:27AM -0400, Tom Lane wrote: >> No, SQL_ASCII represents the complete absence of any encoding >> knowledge. With this database setting, changing client_encoding is a >> complete no-op. Postgres will just absorb and re-emit strings exactly >> as they were supplied originally, no matter what client_encoding is. > The documents remain pretty confusing about this, assuming I still > understand the current state of affairs (always a dangerous > assumption). The chart in > <http://developer.postgresql.org/docs/postgres/multibyte.html>, for > instance, says "SQL_ASCII" supports "ASCII". I'm not sure what to do > about this (I've noticed it before, and run into the same quandary). You're right, the documentation basically doesn't explain this at all :-( I'll try to add something. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
