| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> |
| Cc: | Koichi Suzuki <suzuki(dot)koichi(at)oss(dot)ntt(dot)co(dot)jp>, Mark Woodward <pgsql(at)mohawksoft(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: How to avoid transaction ID wrap |
| Date: | 2006-06-07 15:47:45 |
| Message-ID: | 475.1149695265@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> writes:
> Koichi Suzuki wrote:
>> I've once proposed a patch for 64bit transaction ID, but this causes
>> some overhead to each tuple (XMIN and XMAX).
> Did you check performance on 32-bit or 64-bit systems and 64-bit binary
> version of PGSQL? I think that today is not problem to have 64-bit
> architecture and 64-bit ID should increase scalability of Postgres.
The percentage increase in I/O demand is the main reason the patch was
rejected, not so much the arithmetic.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Teodor Sigaev | 2006-06-07 16:51:25 | Proposal to improve multicolumn GiST page split algoriithm. |
| Previous Message | Tom Lane | 2006-06-07 15:45:17 | Re: self-deadlock at FATAL exit of boostrap process on read error |