Tom Lane wrote:
> If we wanted to be entirely anal about this, we could allow SQL_ASCII
> destination with a different source encoding, but not the reverse.
> However, we currently consider that you're on your own to ensure sanity
> when using SQL_ASCII as far as locale goes, so I'm not sure why the
> policy would be different for encoding.
>
>
>
The trouble is that people won't know the provenance of their database.
I think we should try to guarantee as far as possible that if a database
has encoding X then all the data in it is valid in that encoding.
cheers
andrew
