pg_regress/pg_isolation_regress: Fix possible nullptr dereference.

From: Xing Guo <higuoxing(at)gmail(dot)com>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: pg_regress/pg_isolation_regress: Fix possible nullptr dereference.
Date: 2022-11-30 15:02:35
Message-ID: CACpMh+A8cRvtvtOWVAZsCM1DU81GK4DL26R83y6ugZ1osV=ifA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

Attachment Content-Type Size
patch.diff text/plain 1.1 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2022-11-30 15:02:54 Re: New docs chapter on Transaction Management and related changes
Previous Message Noah Misch 2022-11-30 15:01:36 Re: pgsql: Revoke PUBLIC CREATE from public schema, now owned by pg_databas