Horton

Re: Ltree syntax improvement

Nikita Glukhov <n.gluhov@postgrespro.ru>

View thread View on postgr.es
From: Nikita Glukhov <n.gluhov@postgrespro.ru>
To: Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Cc: Dmitry Belyavsky <beldmit@gmail.com>, Tomas Vondra <tomas.vondra@2ndquadrant.com>, Thomas Munro <thomas.munro@gmail.com>, Alvaro Herrera <alvherre@2ndquadrant.com>, Nikolay Shaplov <dhyan@nataraj.su>
Date: 2020-04-02T13:16:06Z
Lists: pgsql-hackers

Attachments

On 02.04.2020 2:46, Tom Lane wrote:

> Nikita Glukhov <n.gluhov@postgrespro.ru> writes:
>> [ latest version of ltree syntax extension ]
> This is going to need another rebase after all the other ltree hacking
> that just got done.  However, I did include 0001 (use a switch) in
> the commit I just pushed, so you don't need to worry about that.
>
> 			regards, tom lane

Rebased patch attached.

I’m not sure whether it's worth to introduce one LTREE_TOK_SPECIAL for
the whole set of special characters, and still check them with t_iseq().

-- 
Nikita Glukhov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

Commits

  1. Clean up parsing of ltree and lquery some more.