Re: psql crashes found when executing slash commands

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

"K S, Sandhya (Nokia - IN/Bangalore)" <sandhya(dot)k_s(at)nokia(dot)com> writes:
> The issue was with the version of flex(not sure any issue with flex 2.5.37 version).
> We were able to compile with flex version 2.6.4 and it is working without any psql crashes.

Interesting. There are many buildfarm members reporting that they
use 2.5.37, and we've not seen any issues there. Maybe there's a
platform-specific bug in it? Or those members are really running
vendor-patched versions rather than straight 2.5.37? (Hard to
believe they'd all have the same patch though.)

I also remain suspicious that you were running only one of psqlscan.l and
psqlscanslash.l through your local flex, and using the tarball-provided
output file for the other. We currently use flex 2.6.1 when creating
tarballs. It's not real hard to believe that there was an ABI break
between 2.5.x and 2.6.x ...

Dunno that it's worth any extra trouble to track it down, though.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2018-06-13 14:45:05 BUG #15241: PostgreSQL Version 9.6.1 support in Windows 2016 Server
Previous Message Matkar, Prasad L (BHGE) 2018-06-13 14:24:43 BUG #15235: Getting failure message "Restore archive operation failed" while restoring database