| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Greg Stark <gsstark(at)mit(dot)edu> |
| Cc: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net>, ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org, heikki(at)enterprisedb(dot)com |
| Subject: | Re: Another idea for dealing with cmin/cmax |
| Date: | 2006-10-02 15:20:24 |
| Message-ID: | 11015.1159802424@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Greg Stark <gsstark(at)mit(dot)edu> writes:
> The plan Gavin Sherry and I were discussing at the Code Sprint was to store a
> single "most common xmin" xmin in the per-page special area. Then have a bit
> on each tuple indicating that the xmin isn't present in the tuple and instead
> to use the xmin from the page footer. Any tuples with other values of xmin
> would have to store that xmin normally.
This seems pretty unworkable --- anything that involves more than one
field layout for tuple headers is going to be a huge PITA.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-10-02 15:38:45 | Re: Update using sub-select table in schema |
| Previous Message | Tom Lane | 2006-10-02 15:13:57 | Re: src/tools/msvc usage instructions |