fix for BUG #3720: wrong results at using ltree

Filip Rembiałkowski <filip.rembialkowski@gmail.com>

From: Filip Rembiałkowski <filip.rembialkowski@gmail.com>

To: Pgsql Hackers <pgsql-hackers@postgresql.org>

Date: 2019-03-05T21:27:02Z

Lists: pgsql-hackers

Attachments

postgresql-ltree-exclam.20190305.patch (text/x-patch) patch

Hi all,

Here is my attempt to fix a 12-years old ltree bug (which is a todo item).

I see it's not backward-compatible, but in my understanding that's
what is documented. Previous behavior was inconsistent with
documentation (where single asterisk should match zero or more
labels).

http://archives.postgresql.org/pgsql-bugs/2007-11/msg00044.php

Commits

Back-patch addition of stack overflow and interrupt checks for lquery.
- fade4d4dffca 11.8 landed
- e48ff22d39db 9.6.18 landed
- cffa57f52cc4 9.5.22 landed
- 94c9152dc880 12.3 landed
- 8b902e438608 10.13 landed
Fix lquery's NOT handling, and add ability to quantify non-'*' items.
- 70dc4c509b33 13.0 landed
Improve error messages in ltree_in and lquery_in.
- e07e2a40bd0c 13.0 landed
Fix lquery's behavior for consecutive '*' items.
- 9950c8aadf0e 13.0 landed
Protect against overflow of ltree.numlevel and lquery.numlevel.
- 8e1e630d004e 9.5.22 landed
- 95f7ddfdad99 13.0 landed
- 5feb3d0b3f6b 11.8 landed
- 39491aa0da48 9.6.18 landed
- 2bb6bdbe5da7 12.3 landed
- 2618ac6c6535 10.13 landed