From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Peter Geoghegan <pg(at)bowt(dot)ie>, Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org> |
Subject: | Re: [PATCH] Clarify the behavior of the system when approaching XID wraparound |
Date: | 2023-10-16 18:06:01 |
Message-ID: | CA+TgmoZBg95FiR9wVQPAXpGPRkacSt2okVge+PKPPFppN7sfnQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Oct 13, 2023 at 5:03 AM Aleksander Alekseev
<aleksander(at)timescale(dot)com> wrote:
> > Thanks for working on this. I will be relieved once this is finally
> > taken care of.
>
> +1, and many thanks for your attention to the patchset and all the details!
Cool. I committed that and back-patched to v14, and here's the rest.
0001 makes the terminology change that I proposed earlier, and then
0002 is the remainder of what was in the previous patch set that
wasn't covered by what I committed already, with a few adjustments.
In particular, I preferred to stick with "avoid" rather than changing
to "prevent," and I thought it was clearer to refer to "failures"
plural rather than "failure" collective. These are arguable decisions,
though.
I propose to commit these changes only to master. I have included a
fairly long paragraph about that in the commit message for 0002.
--
Robert Haas
EDB: http://www.enterprisedb.com
Attachment | Content-Type | Size |
---|---|---|
v11-0002-Reword-messages-about-impending-M-XID-exhaustion.patch | application/octet-stream | 8.3 KB |
v11-0001-Talk-about-assigning-rather-than-generating-new-.patch | application/octet-stream | 2.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2023-10-16 18:18:38 | Re: Improving Physical Backup/Restore within the Low Level API |
Previous Message | Laurenz Albe | 2023-10-16 17:28:06 | Re: Rename backup_label to recovery_control |