Re: psql crashes found when executing slash commands

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Sergei Kornilov <sk(at)zsrv(dot)org>, "K S, Sandhya (Nokia - IN/Bangalore)" <sandhya(dot)k_s(at)nokia(dot)com>, "'pgsql-bugs(at)postgresql(dot)org'" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: psql crashes found when executing slash commands
Date: 2018-06-06 14:48:09
Message-ID: 7090.1528296489@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Michael Paquier <michael(at)paquier(dot)xyz> writes:
> On Wed, Jun 06, 2018 at 10:42:41AM +0300, Sergei Kornilov wrote:
>> Hmm. What operating system are you using? Hardware architecture? Do
>> you compile postgresql yourself or install some precompiled packages?
>> We have tests for psql slash-commands and they are not broken.

> My bet is on an issue with the version of flex used for compilation, and
> that those binaries have been manually compiled.

psql does some, um, interesting stuff with sharing lexer state between
separately-built flex lexers. I would not be too surprised if it crashes
if you build psqlscan.l and psqlscanslash.l with different versions of
flex, or perhaps even just different flex switches. So that might be an
avenue to check into.

Another theory is that the OP is using something that's not flex at all,
or is some version we've never seen before, and this coding technique
doesn't work at all with it :-(

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2018-06-06 15:28:13 Re: Unnecessarily imprecise stats for very small tables leading to bad plans
Previous Message Tom Lane 2018-06-06 14:38:13 Re: BUG #15225: [XX000] ERROR: invalid DSA memory alloc request size 1073741824 / Where: parallel worker