This is a discussion on pgsql: Adjust DatumGetBool macro so that it isn't fooled by garbage in within the pgsql Committers forums, part of the PostgreSQL category; --> Log Message: ----------- Adjust DatumGetBool macro so that it isn't fooled by garbage in the Datum to the left ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| 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. Modified Files: -------------- pgsql/src/include: postgres.h (r1.77 -> r1.78) (http://developer.postgresql.org/cvsw...1=1.77&r2=1.78) ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match |
| Thread Tools | |
| Display Modes | |
|
|