Skip site navigation (1) Skip section navigation (2)

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: E1P8ePn-0001RG-Lq@gemulon.postgresql.org (view raw or flat)
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_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

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group