pgsql: If pk is NULL, the backend would segfault when accessing ->algo - Mailing list pgsql-committers

From Heikki Linnakangas
Subject pgsql: If pk is NULL, the backend would segfault when accessing ->algo
Date
Msg-id E1P8ePn-0001RK-Ma@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
If pk is NULL, the backend would segfault when accessing ->algo and the
following NULL check was never reached.

This problem was found by Coccinelle (null_ref.cocci from coccicheck).

Marti Raudsepp

Branch
------
REL8_1_STABLE

Details
-------
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=62f86b32ea249bb207a4a6b3f6b4f675af64e523

Modified Files
--------------
contrib/pgcrypto/pgp-pubenc.c |    4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)


pgsql-committers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: pgsql: If pk is NULL, the backend would segfault when accessing ->algo
Next
From: Bruce Momjian
Date:
Subject: pgsql: Clean up pg_upgrade cache lookup code; remove useless NULL poin