Neil Conway <[EMAIL PROTECTED]> writes:As far as I remember (couldn't find modern documentation on the matter) Valgrind is resitant to this problem. When a block of memory is copied, the initialized/uninitialized status is copied along. It only complains when an actual operation is performed using uninitialized memory. This was developed for the explicit reason of avoiding the problem you describe.
Any thoughts on what could be causing these errors?
I suspect valgrind is complaining because XLogInsert is memcpy'ing a
struct that has allocation padding in it. Which of course is a bogus
complaint ...
Shachar
-- Shachar Shemesh Lingnu Open Source Consulting http://www.lingnu.com/
---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match