pgsql: ecpg: fix some minor mishandling of bad input in preprocessor.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: ecpg: fix some minor mishandling of bad input in preprocessor.
Date: 2024-10-16 16:25:09
Message-ID: E1t16ph-0016wW-LA@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

ecpg: fix some minor mishandling of bad input in preprocessor.

Avoid null-pointer crash when considering a cursor declaration
that's outside any C function (a case which is useless anyway).

Ensure a cursor for a prepared statement is marked as initially
not open. At worst, if we chanced to get not-already-zeroed memory
from malloc(), this oversight would result in failing to issue a
"cursor "foo" has been declared but not opened" warning that would
have been appropriate.

Avoid running off the end of the buffer when there are mismatched
square brackets following a variable name. This could lead to
SIGSEGV after reaching the end of memory.

Given the lack of field complaints, none of these seem to be worth
back-patching, but let's clean them up in HEAD.

Per valgrind testing by Alexander Lakhin.

Discussion: https://postgr.es/m/5f5bcecd-d7ec-b8c0-6c92-d1a7c6e0f639@gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/9b4bf5169064044ff082c61bf0783c4a65c08734

Modified Files
--------------
src/interfaces/ecpg/preproc/ecpg.header | 3 ++-
src/interfaces/ecpg/preproc/ecpg.trailer | 1 +
src/interfaces/ecpg/preproc/variable.c | 3 +++
3 files changed, 6 insertions(+), 1 deletion(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Masahiko Sawada 2024-10-16 19:09:55 pgsql: Reduce memory block size for decoded tuple storage to 8kB.
Previous Message Peter Geoghegan 2024-10-16 16:18:16 pgsql: Normalize nbtree truncated high key array behavior.