Re: fix for BUG #3720: wrong results at using ltree

From: Nikita Glukhov <n(dot)gluhov(at)postgrespro(dot)ru>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Filip Rembiałkowski <filip(dot)rembialkowski(at)gmail(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Cc: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, Oleg Bartunov <obartunov(at)postgrespro(dot)ru>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Teodor Sigaev <teodor(at)sigaev(dot)ru>
Subject: Re: fix for BUG #3720: wrong results at using ltree
Date: 2020-03-30 21:46:12
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 30.03.2020 21:00, Tom Lane wrote:

> Hence, new patch versions that do it like that. (0002 is unchanged.)

I tried to simplify a bit loops in checkCond() by merging two of them into
one with an explicit exit condition. Also I added return statement after
this loop, so it's now clear that we can't fall into next "while" loop.

The rest code in 0001 and 0002 is unchanged.

Nikita Glukhov
Postgres Professional:
The Russian Postgres Company

Attachment Content-Type Size
0001-rationalize-ltree-input-errors-3.patch text/x-patch 11.1 KB
0002-ltree-not-fixes-and-better-quantifiers-3.patch text/x-patch 23.9 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2020-03-30 21:59:26 Re: fix for BUG #3720: wrong results at using ltree
Previous Message Tom Lane 2020-03-30 21:20:17 Re: extension patch of CREATE OR REPLACE TRIGGER