Re: BUG #19612: SEGV in ParseConfigFp() in guc-file.l

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Andrey Rachitskiy <pl0h0yp1(at)gmail(dot)com>, ilia(dot)kashintsev(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19612: SEGV in ParseConfigFp() in guc-file.l
Date: 2026-08-16 14:32:14
Message-ID: 343802.1786890734@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Michael Paquier <michael(at)paquier(dot)xyz> writes:
> It seems to me that we should also have a `goto cleanup` if
> yylex_init() fails, also pointing at d663f150b5ed that has switched
> the scanner to be reentrant where yylex_init() has been added.

Yeah. The other thing not being covered here is the possibility
that yy_create_buffer fails and returns NULL.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andrey Borodin 2026-08-16 15:03:15 Re: BUG #19613: pg_restore: several SEGVs in ReadToc() in pg_backup_archiver.c
Previous Message Andrey Rachitskiy 2026-08-16 14:29:25 Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY