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

From: Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: If pk is NULL, the backend would segfault when accessing ->algo
Date: 2010-10-20 19:33:35
Message-ID: [email protected]
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: 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_3_STABLE

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

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

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2010-10-20 20:02:39 pgsql: Clean up pg_upgrade cache lookup code; remove useless NULL poin
Previous Message Tom Lane 2010-10-20 16:49:55 pgsql: Don't try to fetch database name when SetTransactionIdLimit() is