Re: strpos behavior change around empty substring in PG12

2019-10-29 Thread Shay Rojansky
Thanks for the quick turnaround! Tom Lane schrieb am Mo., 28. Okt. 2019, 16:57: > Robert Haas writes: > > On Mon, Oct 28, 2019 at 11:02 AM Shay Rojansky wrote: > >> Before PG12, select strpos('test', '') returns 1 (empty substring found > at first position of the string), whereas starting with

Re: strpos behavior change around empty substring in PG12

2019-10-29 Thread Heikki Linnakangas
On 28/10/2019 17:57, Tom Lane wrote: Robert Haas writes: On Mon, Oct 28, 2019 at 11:02 AM Shay Rojansky wrote: Before PG12, select strpos('test', '') returns 1 (empty substring found at first position of the string), whereas starting with PG12 it returns 0 (empty substring not found). It

Re: strpos behavior change around empty substring in PG12

2019-10-28 Thread Tom Lane
Robert Haas writes: > On Mon, Oct 28, 2019 at 11:02 AM Shay Rojansky wrote: >> Before PG12, select strpos('test', '') returns 1 (empty substring found at >> first position of the string), whereas starting with PG12 it returns 0 >> (empty substring not found). > It looks to me like this got bro

Re: strpos behavior change around empty substring in PG12

2019-10-28 Thread Robert Haas
On Mon, Oct 28, 2019 at 11:02 AM Shay Rojansky wrote: > Before PG12, select strpos('test', '') returns 1 (empty substring found at > first position of the string), whereas starting with PG12 it returns 0 (empty > substring not found). > > Is this behavior change intentional? If so, it doesn't se

strpos behavior change around empty substring in PG12

2019-10-28 Thread Shay Rojansky
Greetings hackers, Before PG12, select strpos('test', '') returns 1 (empty substring found at first position of the string), whereas starting with PG12 it returns 0 (empty substring not found). Is this behavior change intentional? If so, it doesn't seem to be documented in the release notes... F