Re: Proposal: CREATE CONVERSION

> > pg_char_to_encoding() is already in libpq. Or am I missing something?
> 
>  It works with encoding table (pg_enc2name_tbl) and it's compiled 
>  into backend and client too. It means number of encoding is not possible 
>  change after compilation and you (user) can't add new encoding without 
>  pg_enc2name_tbl[] change. I original thought we can add new encodings
>  on-the-fly in 7.3 :-) You're right.
> 
>  IMHO implement "User defined charsets(encodings)" will problem for
>  current libpq design.

No, it's not a libpq problem, but more common "client/server" problem
IMO. It's very hard to share dynamically created object (info)
effectively between client and server.
--
Tatsuo Ishii