From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
Cc: | Gregory Stark <stark(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org, mkoi-pg(at)aon(dot)at |
Subject: | Re: Getting rid of cmin and cmax |
Date: | 2006-09-19 18:04:29 |
Message-ID: | 15071.1158689069@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Heikki Linnakangas <heikki(at)enterprisedb(dot)com> writes:
> As I tried to say in the first post, I believe we can actually get away
> without an entry in local memory in typical scenarios, including bulk
> data loads.
I didn't find that argument very credible, particularly not the part
that assumes we know what the oldest snapshot is. I remain of the
opinion that this is going to be a large, complicated (ie buggy),
poorly performing mechanism to hypothetically someday save 4 bytes
that, even if we do save them, are just going to disappear into
alignment padding on most newer servers.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-09-19 18:09:05 | Re: Odd behavior observed |
Previous Message | Tom Lane | 2006-09-19 17:58:40 | Re: Odd behavior observed |