pgsql: Adjust DatumGetBool macro so that it isn't fooled by garbage in - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Adjust DatumGetBool macro so that it isn't fooled by garbage in
Date
Msg-id 20080325193146.92FFB7558E7@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Adjust DatumGetBool macro so that it isn't fooled by garbage in the Datum
to the left of the actual bool value.  While in most cases there won't be
any, our support for old-style user-defined functions violates the C spec
to the extent of calling functions that might return char or short through
a function pointer declared to return "char *", which we then coerce to
Datum.  It is not surprising that the result might contain garbage
high-order bits ... what is surprising is that we didn't see such cases
long ago.  Per report from Magnus.

This is a back-patch of a change that was made in HEAD almost exactly
a year ago.  I had refrained from back-patching at the time, but now
we find that this is *necessary* for contrib to work with gcc 4.3.

Tags:
----
REL8_0_STABLE

Modified Files:
--------------
    pgsql/src/include:
        postgres.h (r1.70 -> r1.70.4.1)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/postgres.h?r1=1.70&r2=1.70.4.1)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Adjust DatumGetBool macro so that it isn't fooled by garbage in
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Adjust DatumGetBool macro so that it isn't fooled by garbage in