pg_regress/pg_isolation_regress: Fix possible nullptr dereference.
Xing Guo <higuoxing@gmail.com>
From: Xing Guo <higuoxing@gmail.com>
To: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2022-11-30T15:02:35Z
Lists: pgsql-hackers
Attachments
- patch.diff (text/plain) patch
Hi hackers, While playing with pg_regress and pg_isolation_regress, I noticed that there's a potential nullptr deference in both of them. How to reproduce: Specify the `--dbname=` option without providing any database name. <path>/<to>/pg_regress --dbname= foo <path>/<to>/pg_isolation_regress --dbname= foo Patch is attached. -- Best Regards, Xing
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Reject missing database name in pg_regress and cohorts.
- f2f9e11d3522 15.2 landed
- d5515ca7cf1b 16.0 landed
- ae9939020dda 13.10 landed
- a949b7320fdf 14.7 landed
- a587901786d5 12.14 landed
- 04f3acc97e42 11.19 landed