Re: invalidly encoded strings - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: invalidly encoded strings
Date
Msg-id 46E57075.7050309@dunslane.net
Whole thread Raw
In response to Re: invalidly encoded strings  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers

Tom Lane wrote:
> OK.  Looking back, there was also some mention of changing chr's
> argument to bigint, but I'd counsel against doing that.  We should not
> need it since we only support 4-byte UTF8, hence code points only up to
> 21 bits (and indeed even 6-byte UTF8 can only have 31-bit code points,
> no?).
>
>
>   

Yes, that was a thinko on my part. I realised that yesterday.

cheers

andrew


pgsql-hackers by date:

Previous
From: "Heikki Linnakangas"
Date:
Subject: Ts_rank internals
Next
From: Tom Lane
Date:
Subject: Re: Maybe some more low-hanging fruit in the latestCompletedXid patch.