Tom Lane wrote: >> I don't know what it should be doing if it can't find a match, so I >> haven't changed that behavior. > > As things stand, it should throw error, except in the case of SQL_ASCII; > there is no excuse for any other database encoding to not be in the > table. However, what seems more worrisome to me is the prospect already > discussed that the codeset name we have in the table is not actually > recognized by gettext/iconv. Did we have a solution for that? > > Anyway, this fixes my immediate concern about where the info is located, > so you may as well apply it with the array-terminator fix.
Done. //Magnus -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
