From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
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-12 00:33:31 |
Message-ID: | 20200512003331.GK4666@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, May 10, 2020 at 03:09:47PM -0500, Justin Pryzby wrote:
> > 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.
> ...
OK, fixed to be:
In ltree, when using adjacent asterisks with braces, e.g. ".*{2}.*{3}",
properly interpret that as ".*{5}" (Nikita Glukhov)
I added two dots.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2020-05-12 00:33:40 | Re: PG 13 release notes, first draft |
Previous Message | Bruce Momjian | 2020-05-12 00:22:46 | Re: PG 13 release notes, first draft |