Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Except that the entire point of this patch is to dumb down NextChar to
>> be the same as NextByte for UTF8 strings.

> That's not what I see in (what I think is) the latest submission, which 
> includes this snippet:

[ scratches head... ]  OK, then I think I totally missed what this patch
is trying to accomplish; because this code looks just the same as the
existing multibyte-character operations.  Where does the performance
improvement come from?

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Reply via email to