On Fri, Aug 24, 2018 at 05:14:46PM -0400, Viktor Dukhovni wrote:
> On Fri, Aug 24, 2018 at 04:54:32PM -0400, Wietse Venema wrote:
>
> > I think that we should by default extend this to all lookup tables
> > and do away with that LATIN1 hack. That would also address the
> > problem that underlies the original request. No need for signaling
> > the request encoding!
>
> If the Postgres dictionary client-encoding changes from LATIN1 to
> UTF8, at what layer do you want to convert "unspecified" non-ASCII
> lookup keys UTF8 (by encoding each non-ASCII byte to 2 UTF-8 bytes)?
>
> If we don't do that, we'll get dictionary lookup errors for invalid
> input strings, rather than no-match...
It seems you just want to skip the lookup instead... I guess that'll
work too.
--
Viktor.
