Re: PG 13 release notes, first draft (ltree dot star)

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: PG 13 release notes, first draft (ltree dot star)
Date: 2020-05-10 20:09:47
Message-ID: 20200510200947.GD18456@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> In ltree, when using adjacent asterisks with braces, e.g. "*{2}.*{3}", properly interpret that as "*{5}" (Nikita Glukhov)

I think that should say ".*" not "*", as in:

> In ltree, when using adjacent asterisks with braces, e.g. ".*{2}.*{3}", properly interpret that as "*{5}" (Nikita Glukhov)

The existing text clearly came from the commit message, which (based on its
regression tests) I think was the source of the missing dot.

commit 9950c8aadf0edd31baec74a729d47d94af636c06
Author: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Date: Sat Mar 28 18:31:05 2020 -0400

Fix lquery's behavior for consecutive '*' items.

Something like "*{2}.*{3}" should presumably mean the same as
"*{5}", but it didn't. Improve that.
...

--
Justin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2020-05-10 20:20:53 calling procedures is slow and consumes extra much memory against calling function
Previous Message Tom Lane 2020-05-10 19:07:17 Re: Back-branch minor release notes are up for review