Re: jsonpath
От | Alexander Korotkov |
---|---|
Тема | Re: jsonpath |
Дата | |
Msg-id | CAPpHfdu-MvmN9pJnTtTCyuzbcF4t2K4hsfMdEtTGjfx7ZbGVYw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: jsonpath (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>) |
Ответы |
Re: jsonpath
RE: jsonpath RE: jsonpath Re: jsonpath |
Список | pgsql-hackers |
On Thu, Mar 28, 2019 at 7:43 PM Andrew Dunstan <andrew.dunstan@2ndquadrant.com> wrote: > On 3/28/19 9:50 AM, Tom Lane wrote: > > Andres Freund <andres@anarazel.de> writes: > >> On March 28, 2019 9:31:14 AM EDT, Tom Lane <tgl@sss.pgh.pa.us> wrote: > >>> Has anybody gotten through a valgrind run on this code yet? > >> Skink has successfully passed since - but that's x86... > > Yeah, there is a depressingly high chance that this is somehow specific > > to the bison version, flex version, and/or compiler in use on jacana. > > lousyjack has also passed it (x64). > > git bisect on jacana blames commit 550b9d26f. Hmm... 550b9d26f just makes jsonpath_gram.y and jsonpath_scan.l compile at once. I've re-read this commit and didn't find anything suspicious. I've asked Andrew for access to jacana in order to investigate this myself. ------ Alexander Korotkov Postgres Professional: http://www.postgrespro.com The Russian Postgres Company
В списке pgsql-hackers по дате отправления: