On Dec 16, 2010, at 8:19 AM, Tom Lane wrote: > I would think that we want to establish the same policy as we have for > dictionary files: they're assumed to be UTF-8. I don't believe there > should be an encoding option at all. If we didn't need one for > dictionary files, there is *surely* no reason why we have to have one > for extension SQL files.
+1 KISS. David -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
