| From: | "Finnerty, Jim" <jfinnert(at)amazon(dot)com> |
|---|---|
| To: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Challenges preventing us moving to 64 bit transaction id (XID)? |
| Date: | 2021-01-26 19:06:57 |
| Message-ID: | F46F2088-302B-4959-A7E2-41C9A328ABC8@amazon.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Here are the remaining parts of the original 64bit XID patch set that I was able to apply manually, albeit with TBD's and FIXME's. I was unable to apply some small parts of the original patch set. What is contained here should 'git apply' cleanly today, but doesn't compile. It documents most of what was done with this approach in the hope that it will inform a future 64-bit table AM implementation about the many things that need to be considered.
| Attachment | Content-Type | Size |
|---|---|---|
| 64bit-xid-big-diff.patch | application/octet-stream | 87.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bossart, Nathan | 2021-01-26 19:13:57 | Re: archive status ".ready" files may be created too early |
| Previous Message | John Naylor | 2021-01-26 18:52:53 | Re: WIP: BRIN multi-range indexes |