| From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: Getting rid of LSEG.m |
| Date: | 2015-02-03 16:52:48 |
| Message-ID: | 54D0FCE0.4010507@vmware.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 02/03/2015 06:47 PM, Tom Lane wrote:
> 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.
+1 for removing it altogether.
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-02-03 16:53:06 | Re: Release note bloat is getting out of hand |
| Previous Message | Tom Lane | 2015-02-03 16:47:40 | Getting rid of LSEG.m |