Re: Speeding up text_position_next with multibyte encodings - Mailing list pgsql-hackers

From John Naylor
Subject Re: Speeding up text_position_next with multibyte encodings
Date
Msg-id CAJVSVGV0bG8ZBz1H--FaiOdp25W1eSwcPTO3sQSP+TNLScbuYQ@mail.gmail.com
Whole thread Raw
In response to Re: Speeding up text_position_next with multibyte encodings  (John Naylor <jcnaylor@gmail.com>)
Responses Re: Speeding up text_position_next with multibyte encodings  (Heikki Linnakangas <hlinnaka@iki.fi>)
List pgsql-hackers
On 12/14/18, John Naylor <jcnaylor@gmail.com> wrote:
> I signed up to be a reviewer, and I will be busy next month, so I went
> ahead and fixed the typo in the patch that broke assert-enabled
> builds. While at it, I standardized on the spelling "start_ptr" in a
> few places to match the rest of the file. It's a bit concerning that
> it wouldn't compile with asserts, but the patch was written by a
> committer and seems to work.

I just noticed that the contrib/citext test fails. I've set the status
to waiting on author.

-John Naylor


pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: valgrind issues on Fedora 28
Next
From: Robert Haas
Date:
Subject: Re: Bogus EPQ plan construction in postgres_fdw