Getting rid of LSEG.m - Mailing list pgsql-hackers

From Tom Lane
Subject Getting rid of LSEG.m
Date
Msg-id 5078.1422982060@sss.pgh.pa.us
Whole thread Raw
Responses Re: Getting rid of LSEG.m  (Heikki Linnakangas <hlinnakangas@vmware.com>)
List pgsql-hackers
I noticed a Coverity complaint about the "m" field of LSEG being
uninitialized, which indeed it is because all the places that
would set it are ifdef'd out.  So why didn't the field itself
get ifdef'd out as well?

Or perhaps we should just remove both the field and the ifdef'd
assignments.  That's a bit more drastic but I can't really see
this code ever coming back to life ... especially since the notion
of a field that's not stored on disk but is valid in in-memory
copies seems impossibly error-prone.  Most functions can have no
idea whether their input is residing in a disk buffer or not.
And adding the bookkeeping to determine that would surely cost
more than just recomputing the slope when needed.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Petr Jelinek
Date:
Subject: Re: Redesigning checkpoint_segments
Next
From: Heikki Linnakangas
Date:
Subject: Re: Getting rid of LSEG.m