| From: | ITAGAKI Takahiro <itagaki(dot)takahiro(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | postgres(at)cybertec(dot)at, pgsql-patches(at)postgresql(dot)org |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Koichi Suzuki <koichi(at)intellilink(dot)co(dot)jp>, Satoshi Nagayasu <nagayasus(at)nttdata(dot)co(dot)jp>, ikubo(at)intellilink(dot)co(dot)jp, yasunaga <yasunaga(dot)hisato(at)soft(dot)fujitsu(dot)com>, Bruce Momjian <root(at)candle(dot)pha(dot)pa(dot)us>, Jan Wieck <JanWieck(at)Yahoo(dot)com>, sakata(dot)tetsuo(at)lab(dot)ntt(dot)co(dot)jp, "T(dot)Honishi" <honishi(dot)takashi(at)lab(dot)ntt(dot)co(dot)jp> |
| Subject: | Re: A couple of patches for PostgreSQL 64bit support |
| Date: | 2005-07-08 00:38:07 |
| Message-ID: | 20050708093449.3CC4.ITAGAKI.TAKAHIRO@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Hans-J|rgen Schvnig <postgres(at)cybertec(dot)at> wrote:
> 64-bit XIDs seem to be an overkill - the only practical impact I can see
> is an even larger tuple header (this can be an issue on large boxes too
> - at least compared to Oracle).
I agreed, too. The changes of XIDs cannot be ignored because the overhead
will be 32bytes per tuple.
Avoiding overheads, can XIDs/CIDs be different bit length? For example,
can XIDs/CIDs be changed to 48/16-bit or 40/24-bit?
---
ITAGAKI Takahiro
NTT Cyber Space Laboratories
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Kirkwood | 2005-07-08 01:15:06 | Re: Pg_autovacuum on FreeBSD |
| Previous Message | Koichi Suzuki | 2005-07-08 00:36:10 | Re: A couple of patches for PostgreSQL 64bit support |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2005-07-08 02:37:04 | Re: A couple of p.tches for PostgreSQL 64bit support |
| Previous Message | Koichi Suzuki | 2005-07-08 00:36:10 | Re: A couple of patches for PostgreSQL 64bit support |