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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
Cc: Alexander Korotkov <akorotkov(at)postgresql(dot)org>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Get rid of backtracking in jsonpath_scan.l
Date: 2019-03-26 14:21:25
Message-ID: 20109.1553610085@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> writes:
> On 3/25/19 8:44 AM, Alexander Korotkov wrote:
>> Get rid of backtracking in jsonpath_scan.l

> jacana appears to be having trouble with this:

I wonder if that's related to the not-very-reproducible failures
we've seen on snapper. Can you get a stack trace?

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Alvaro Herrera 2019-03-26 14:27:40 pgsql: Improve psql's \d display of foreign key constraints
Previous Message Tom Lane 2019-03-26 13:18:26 Re: pgsql: Fix misplaced const

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2019-03-26 14:31:10 Re: [HACKERS] Block level parallel vacuum
Previous Message Daniel Gustafsson 2019-03-26 14:16:00 Re: Shouldn't current_schema() be at least PARALLEL RESTRICTED?