In addition to/instead of abstracting cmin/cmax to a phantom ID, what
about allowing for two versions of the tuple header, one with cid info
and one without? That would allow for cid info to be stripped out when
pages were written to disk.
The downside to this is that we'd have to be able to deal with pages
in-memory potentially being larger than pages on-disk. Since there's
been discussion of separating on-disk and in-memory page formats, maybe
that doesn't kill the proposal outright.
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgsql-hackers by date
|Next:||From: Heikki Linnakangas||Date: 2006-09-28 16:13:11|
|Subject: Re: Another idea for dealing with cmin/cmax|
|Previous:||From: Tom Lane||Date: 2006-09-28 16:06:49|
|Subject: Re: Row IS NULL question |