| From: | "Finnerty, Jim" <jfinnert(at)amazon(dot)com> |
|---|---|
| To: | Maxim Orlov <orlovmg(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add 64-bit XIDs into PostgreSQL 15 |
| Date: | 2022-01-04 17:49:07 |
| Message-ID: | 90BAF0BF-69DF-45C4-821C-76A487210682@amazon.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Maxim,
I’m glad to see that you’re trying to carry the 64-bit XID work forward. I had not noticed that my earlier patch (also derived from Alexander Kortkov’s patch) was responded to back in September. Perhaps we can merge some of the code cleanup that it contained, such as using XID_FMT everywhere and creating a type for the kind of page returned by TransactionIdToPage() to make the code cleaner.
Is your patch functionally the same as the PostgresPro implementation? If so, I think it would be helpful for everyone’s understanding to read the PostgresPro documentation on VACUUM. See in particular section “Forced shrinking pg_clog and pg_multixact”
https://postgrespro.com/docs/enterprise/9.6/routine-vacuuming#vacuum-for-wraparound
best regards,
/Jim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Lakhin | 2022-01-04 19:00:00 | Re: Proposal: remove obsolete hot-standby testing infrastructure |
| Previous Message | Erik Rijkers | 2022-01-04 17:10:07 | biblio.sgml dead link |