Postgres Pro
Downloads
Home   >   mailing lists

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-0001RG-Lq@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Tree view 
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_2_STABLE

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

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

pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Don't try to fetch database name when SetTransactionIdLimit() is
Next
From: Heikki Linnakangas
Date:
Subject: pgsql: If pk is NULL, the backend would segfault when accessing ->algo