Hi pgsql-hackers,
Following the patch to implement strpos with Boyer-Moore-Horspool,
it was proposed we bring BMH to LIKE as well.
Original thread:
https://www.postgresql.org/message-id/flat/27645.1220635769%40sss.pgh.pa.us#27645.1220635...@sss.pgh.pa.us
I'm a first time hacker and I found this
I agree, should we remove it from the TODO list?
On Mon, Aug 1, 2016 at 6:13 PM, Robert Haas wrote:
> On Mon, Aug 1, 2016 at 1:19 PM, Karan Sikka wrote:
> > Following the patch to implement strpos with Boyer-Moore-Horspool,
> > it was proposed we bring BMH to LIKE as well.
&
On Tue, Aug 2, 2016 at 1:56 PM, Alvaro Herrera
wrote:
> Robert Haas wrote:
> > On Mon, Aug 1, 2016 at 1:19 PM, Karan Sikka
> wrote:
> > > Following the patch to implement strpos with Boyer-Moore-Horspool,
> > > it was proposed we bring BMH to LIKE as wel
> Having said that, I've had a bee in my bonnet for a long time about
> removing per-row setup cost for repetitive regex matches, and
> whatever infrastructure that needs would work for this too.
What are the per-row setup costs for regex matches? I looked at
`regexp.c` and saw:
```
/*
* We cach
