| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
| Cc: | Aleksander Alekseev <aleksander(at)timescale(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com> |
| Subject: | Re: [PATCH] Clarify the behavior of the system when approaching XID wraparound |
| Date: | 2023-09-20 03:41:07 |
| Message-ID: | CAH2-WzncAJjwqx8ictxOyqV6KNL=i7+78H8tniHSNPEz5oqUmw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, May 14, 2023 at 6:06 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> BTW, Google cloud already just instruct their users to ignore the
> xidStopLimit HINT about single user mode:
>
> https://cloud.google.com/sql/docs/postgres/txid-wraparound
I read this just today, and was reminded of this thread:
It reads:
"1. Transaction ID wraparound: PostgreSQL transaction IDs or XIDs are
32-bit unsigned integers that are assigned to each transaction and
also get incremented. When they reach their maximum value, it would
wrap around to zero (similar to a ring buffer) and can lead to data
corruption."
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2023-09-20 04:39:02 | Re: Fix bug in VACUUM and ANALYZE docs |
| Previous Message | Maciek Sakrejda | 2023-09-20 03:23:44 | Re: CREATE FUNCTION ... SEARCH { DEFAULT | SYSTEM | SESSION } |