neha khatri <nehakhatri5@gmail.com> writes:
> It looks like this validation might not reflect the correct behaviour for a
> well defined conproc for certain encodings.
> e.g. Consider LATIN1 as src_encoding and EBCDIC as dst_encoding in the
> above query.
Um ... well, that's already a bridge too far. Postgres does not support
any encodings that aren't ASCII supersets, and the possibility that we
would do so in future isn't measurably different from zero. There's too
much code that depends on that assumption, and too little benefit to
getting rid of it.
If you can show a problem case that doesn't involve EBCDIC, then I'm
all ears.
regards, tom lane