> On Oct 22, 2020, at 1:09 PM, Tom Lane <t...@sss.pgh.pa.us> wrote:
> 
> ooh, looks like prairiedog sees the problem too.  That means I should be
> able to reproduce it under a debugger, if you're not certain yet where
> the problem lies.

Thanks, Tom, but I question whether the regression test failures are from a 
problem in the verify_heapam.c code.  I think they are a busted perl test.  The 
test was supposed to corrupt the heap by overwriting a heap file with a large 
chunk of garbage, but in fact only wrote a small amount of garbage.  The idea 
was to write about 2000 bytes starting at offset 32 in the page, in order to 
corrupt the line pointers, but owing to my incorrect use of syswrite in the 
perl test, that didn't happen.

I think the uninitialized variable warning is warning about a real problem in 
the c-code, but I have no reason to think that particular problem is causing 
this particular regression test failure.

—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company





Reply via email to