Re: pgsql: Get rid of backtracking in jsonpath_scan.l

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Alexander Korotkov <akorotkov(at)postgresql(dot)org>
Cc: pgsql-committers <pgsql-committers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgsql: Get rid of backtracking in jsonpath_scan.l
Date: 2019-03-25 12:55:45
Message-ID: CA+TgmoYprcXtvjmJwAkQDCVxMEXBPT5gLGFuiL_eTMauZCPKWw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Mon, Mar 25, 2019 at 8:44 AM Alexander Korotkov
<akorotkov(at)postgresql(dot)org> wrote:
> Discussion: https://mail.google.com/mail/u/0?ik=a20b091faa&view=om&permmsgid=msg-f%3A1628425344167939063

This is really a pretty evil link to include in a commit message.
When I clicked on it, it logged me out of my gmail account.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Alexander Korotkov 2019-03-25 12:58:12 Re: pgsql: Get rid of backtracking in jsonpath_scan.l
Previous Message Alexander Korotkov 2019-03-25 12:44:08 pgsql: Get rid of backtracking in jsonpath_scan.l

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Korotkov 2019-03-25 12:58:12 Re: pgsql: Get rid of backtracking in jsonpath_scan.l
Previous Message Sergei Kornilov 2019-03-25 12:45:21 Re: ALTER TABLE with ADD COLUMN and ADD PRIMARY KEY USING INDEX throws spurious "column contains null values"