Thread: pgsql: libpq was not consistently checking for memory allocation
pgsql: libpq was not consistently checking for memory allocation
From
neilc@svr1.postgresql.org (Neil Conway)
Date:
Log Message:
-----------
libpq was not consistently checking for memory allocation failures. This
patch adds missing checks to the call sites of malloc(), strdup(),
PQmakeEmptyPGresult(), pqResultAlloc(), and pqResultStrdup(), and updates
the documentation. Per original report from Volkan Yazici about
PQmakeEmptyPGresult() not checking for malloc() failure.
Modified Files:
--------------
pgsql/doc/src/sgml:
libpq.sgml (r1.184 -> r1.185)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/libpq.sgml.diff?r1=1.184&r2=1.185)
pgsql/src/interfaces/libpq:
fe-connect.c (r1.309 -> r1.310)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/fe-connect.c.diff?r1=1.309&r2=1.310)
fe-exec.c (r1.168 -> r1.169)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/fe-exec.c.diff?r1=1.168&r2=1.169)
fe-misc.c (r1.113 -> r1.114)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/fe-misc.c.diff?r1=1.113&r2=1.114)
fe-print.c (r1.59 -> r1.60)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/fe-print.c.diff?r1=1.59&r2=1.60)
fe-protocol2.c (r1.17 -> r1.18)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/fe-protocol2.c.diff?r1=1.17&r2=1.18)
fe-protocol3.c (r1.20 -> r1.21)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/fe-protocol3.c.diff?r1=1.20&r2=1.21)
libpq-int.h (r1.101 -> r1.102)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/libpq-int.h.diff?r1=1.101&r2=1.102)