| From: | Andreas Kretschmer <andreas(at)a-kretschmer(dot)de> |
|---|---|
| To: | pgsql-novice(at)lists(dot)postgresql(dot)org |
| Subject: | Re: transaction wraparound |
| Date: | 2019-10-31 10:14:06 |
| Message-ID: | 672b85ae-9c3f-6a1b-6e20-1f5999490198@a-kretschmer.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
Am 31.10.19 um 08:15 schrieb Павел Ерёмин:
> Hi.
> I apologize for my English.
> I have a question about transaction wraparound. As far as I know,
> transaction numbers are 32 bit, which greatly limits their number. In
> the tuple header there are now t_xmin and t_xmax fields - both 32
> bits each. So why not replace them with a single field with a
> transaction number of 64 bits length - this is the transaction number
> that created the version ( this is exactly what the MS SQL server
> does)? In this case, you do not have to lengthen header tuple. Of
> course, this can result in increased I/O, so to compensate for it, you
> can turn off buffered read (O_DIRECT) while reading.
and how to handle deleted/updated tuple?
Regards, Andreas
--
2ndQuadrant - The PostgreSQL Support Company.
www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2019-10-31 18:59:36 | Re: transaction wraparound |
| Previous Message | Павел Ерёмин | 2019-10-31 07:15:45 | transaction wraparound |