Re: Missing NULL check after calling ecpg_strdup
Aleksander Alekseev <aleksander@tigerdata.com>
From: Aleksander Alekseev <aleksander@tigerdata.com>
To: pgsql-hackers@lists.postgresql.org
Cc: Álvaro Herrera <alvherre@kurilemu.de>, Evgeniy Gorbanev <gorbanyoves@basealt.ru>
Date: 2025-07-14T14:03:44Z
Lists: pgsql-hackers
Attachments
- v4-0001-Add-proper-checks-for-ecpg_strdup-return-value.patch (text/x-patch) patch v4-0001
Hi Alvaro, > This looks super baroque. Why not simplify a bit instead? Maybe > something like > > [...] Fair point. Here is the corrected patch.
Commits
-
ecpg: Improve error detection around ecpg_strdup()
- a6eabec6808c 19 (unreleased) landed
-
ecpg: Fix NULL pointer dereference during connection lookup
- c934d5673894 13.22 landed
- 408fe659a890 14.19 landed
- 0123922f82d2 15.14 landed
- 313d3102facd 16.10 landed
- 2805e1c1edd5 17.6 landed
- 0ded7615d8ca 18.0 landed
- 1b8bbee05d70 19 (unreleased) landed