On Tue, Dec 19, 2023 at 7:58 PM Thomas Munro wrote:
> On Wed, Dec 20, 2023 at 4:41 AM Dominique Devienne
> wrote:
> > On Tue, Dec 19, 2023 at 2:02 PM Thomas Munro
> wrote:
> >> On Wed, Dec 20, 2023 at 1:39 AM Dominique Devienne
> wrote:
> >> > Program received signal SIGSEGV, Segmentation faul
On Wed, Dec 20, 2023 at 4:41 AM Dominique Devienne wrote:
> On Tue, Dec 19, 2023 at 2:02 PM Thomas Munro wrote:
>> On Wed, Dec 20, 2023 at 1:39 AM Dominique Devienne
>> wrote:
>> > Program received signal SIGSEGV, Segmentation fault.
>> > 0x004232b8 in slash_yylex ()
>>
>> I think this
On Tue, Dec 19, 2023 at 2:02 PM Thomas Munro wrote:
> On Wed, Dec 20, 2023 at 1:39 AM Dominique Devienne
> wrote:
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x004232b8 in slash_yylex ()
>
> I think this might have to do with flex changing. Does it help if you
> "make m
Thomas Munro writes:
> On Wed, Dec 20, 2023 at 1:39 AM Dominique Devienne
> wrote:
>> Program received signal SIGSEGV, Segmentation fault.
>> 0x004232b8 in slash_yylex ()
> I think this might have to do with flex changing. Does it help if you
> "make maintainer-clean"?
If that doesn't
On Wed, Dec 20, 2023 at 1:39 AM Dominique Devienne wrote:
> Program received signal SIGSEGV, Segmentation fault.
> 0x004232b8 in slash_yylex ()
I think this might have to do with flex changing. Does it help if you
"make maintainer-clean"?
Hi. We've recently upgraded from libpq 15.2 to 16.1.
We custom build postgresql using the instructions and GCC 9.1 (from RH7's
dts9).
We used the same process for building 15.2 and 16.1.
But somehow psql crashes on any backslash command, while 15.2 works fine.
I've included the small backtrace belo
