Re: Speeding up text_position_next with multibyte encodings

From: John Naylor <jcnaylor(at)gmail(dot)com>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Speeding up text_position_next with multibyte encodings
Date: 2018-12-14 21:40:08
Message-ID: CAJVSVGV0bG8ZBz1H--FaiOdp25W1eSwcPTO3sQSP+TNLScbuYQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12/14/18, John Naylor <jcnaylor(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2018-12-14 22:07:00 Re: Bogus EPQ plan construction in postgres_fdw
Previous Message Tomas Vondra 2018-12-14 21:35:56 Re: valgrind issues on Fedora 28