Getting rid of LSEG.m

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-hackers(at)postgreSQL(dot)org
Subject: Getting rid of LSEG.m
Date: 2015-02-03 16:47:40
Message-ID: 5078.1422982060@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2015-02-03 16:52:48 Re: Getting rid of LSEG.m
Previous Message Petr Jelinek 2015-02-03 16:39:53 Re: Redesigning checkpoint_segments