On ons, 2009-11-18 at 08:52 -0500, Andrew Dunstan wrote: > 4) set the client encoding before the file is read in any of the ways > that have already been discussed and then allow psql to eat the BOM.
This is certainly a workaround, just like piping the file through a suitable sed expression would be, but conceptually, the client encoding is a property of the file and should therefore be marked in the file. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
