Alvaro Herrera <alvhe...@commandprompt.com> writes: > Andrew Dunstan wrote: >> True. It's a workaround, but I think it's acceptable at this stage. >> We need to get some experience with this facility before we can >> refine it.
> Hmm? If we decide now that it's not going to have encoding conversion, > we won't able to change it later. How so? If the feature currently allows only ASCII data, the behavior would be upward compatible with a future version that is able to accept and convert non-ASCII characters. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers