| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: invalidly encoded strings |
| Date: | 2007-09-10 16:27:33 |
| Message-ID: | 46E57075.7050309@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-09-10 16:45:27 | Re: Maybe some more low-hanging fruit in the latestCompletedXid patch. |
| Previous Message | Martijn van Oosterhout | 2007-09-10 16:25:01 | Re: invalidly encoded strings |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2007-09-10 16:27:46 | Yet more tsearch refactoring |
| Previous Message | Martijn van Oosterhout | 2007-09-10 16:25:01 | Re: invalidly encoded strings |