Re: pg17.3 PQescapeIdentifier() ignores len
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Justin Pryzby <pryzby@telsasoft.com>, pgsql-hackers@lists.postgresql.org
Date: 2025-02-14T23:55:55Z
Lists: pgsql-hackers
Hi, On 2025-02-13 14:00:09 -0500, Tom Lane wrote: > Justin Pryzby <pryzby@telsasoft.com> writes: > > The fprintf suggests that since 5dc1e42b4 PQescapeIdentifier ignores its len. > > Ugh, yes. Need something like the attached. I just pushed this fix, together with an expansion of test_escape.c. With the expanded test both uses of strlen() are detected. > FTR, 5dc1e42b4 et al were quite subtle patches done under extreme time > pressure. I wonder if they have any other issues. More eyes on those > patches would be welcome, now that they are public. Indeed. Greetings, Andres Freund
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix PQescapeLiteral()/PQescapeIdentifier() length handling
- 1f7a05324524 13.20 landed
- 985908df1811 14.17 landed
- 22ffbbf24db4 15.12 landed
- 111f4dd273c8 16.8 landed
- a92db3d02dbd 17.4 landed
- efdadeb2238f 18.0 landed