pgsql: Fix potential memory access violation in ecpg if filename of inc

From: Michael Meskes <meskes(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix potential memory access violation in ecpg if filename of inc
Date: 2019-03-11 15:18:43
Message-ID: E1h3MhP-00006n-5m@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix potential memory access violation in ecpg if filename of include file is
shorter than 2 characters.

Patch by: "Wu, Fei" <wufei(dot)fnst(at)cn(dot)fujitsu(dot)com>

Branch
------
REL_11_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/e7adda86ba9c8dc1d0db07d0049ccfff42082a0e

Modified Files
--------------
src/interfaces/ecpg/preproc/pgc.l | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2019-03-11 15:25:38 pgsql: In guc.c, ignore ERANGE errors from strtod().
Previous Message Tom Lane 2019-03-11 15:06:33 Re: Portability of strtod (was Re: pgsql: Include GUC's unit, if it has one, in out-of-range error message)