Fujii Masao <masao.fujii@oss.nttdata.com> writes:
> On 2020/12/03 1:04, Heikki Linnakangas wrote:
>> We never use non-default conversions for anything. All code that performs encoding conversions only cares about the
defaultones.
> Yes. I had to update pg_conversion.condefault directly so that we can
> use custom encoding when I registered it. The direct update of
> pg_conversion is of course not good thing. So I was wondering
> if we should have something like ALTER CONVERSION SET DEFAULT.
Perhaps, but what I'd think is more urgent is having some way for
a session to select a non-default conversion for client I/O.
regards, tom lane
