Re: The "char" type versus non-ASCII characters

On Fri, Dec 03, 2021 at 03:13:24PM -0500, Tom Lane wrote:
> Andrew Dunstan <andrew@dunslane.net> writes:
> > On 12/3/21 14:42, Tom Lane wrote:
> >> Right, I envisioned that ASCII behaves the same but we'd use
> >> a numeric representation for high-bit-set values.  These
> >> cases could be told apart fairly easily by charin(), since
> >> the numeric representation would always be three digits.
> 
> > OK, this seems the most attractive. Can we also allow 2 hex digits?
> 
> I think we should pick one base and stick to it.  I don't mind
> hex if you have a preference for that.
> 
> 			regards, tom lane

+1 for hex

Regards,
Ken