Unitialized Values in record_image_cmp
От | Andres Freund |
---|---|
Тема | Unitialized Values in record_image_cmp |
Дата | |
Msg-id | 20131017130150.GA442708@alap2.anarazel.de обсуждение исходный текст |
Ответы |
Re: Unitialized Values in record_image_cmp
|
Список | pgsql-hackers |
Hi, Valgrind tells me: ==442828== Conditional jump or move depends on uninitialised value(s) ==442828== at 0x80084F: record_image_cmp (rowtypes.c:1521) ==442828== by 0x801522: btrecordimagecmp (rowtypes.c:1839) ==442828== by 0x8C6604: comparison_shim (sortsupport.c:53) ==442828== by 0x64284D: ApplySortComparator (sortsupport.h:143) ==442828== by 0x642F3B: MJCompare (nodeMergejoin.c:412) ==442828== by 0x643A29: ExecMergeJoin (nodeMergejoin.c:1211) ==442828== by 0x62305A: ExecProcNode (execProcnode.c:453) ==442828== by 0x640800: ExecLimit (nodeLimit.c:91) ==442828== by 0x623135: ExecProcNode (execProcnode.c:500) ==442828== by 0x620E15: ExecutePlan (execMain.c:1472) ==442828== by 0x61EF94: standard_ExecutorRun (execMain.c:307) ==442828== by 0x61EE0B: ExecutorRun (execMain.c:255) And a quick look indeed seems to confirm that that's possible. Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: