Re: [UNVERIFIED SENDER] pg_upgrade can result in early wraparound on databases with high transaction load

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, "Drouvot, Bertrand" <bdrouvot(at)amazon(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, Jason Harvey <jason(at)reddit(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, "Tharakan, Robins" <tharar(at)amazon(dot)com>
Subject: Re: [UNVERIFIED SENDER] pg_upgrade can result in early wraparound on databases with high transaction load
Date: 2024-05-17 12:35:42
Message-ID: 6D72E937-528A-4744-B01A-1158ABEFE3A5@yesql.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

> On 16 May 2024, at 19:47, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Yeah, it's not worth working harder than this. I do see one typo
> in your comment: s/supported then/supported when/. LGTM otherwise.

Thanks for review, I've pushed this (with the fix from above) to 14 through 12.

--
Daniel Gustafsson

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Troels Arvin 2024-05-17 12:44:24 utf8 vs UTF-8
Previous Message Laurenz Albe 2024-05-17 11:56:35 Re: Do we have any email discussions related to SQL rate limiting?

Browse pgsql-hackers by date

  From Date Subject
Next Message Joe Conway 2024-05-17 12:42:04 Re: commitfest.postgresql.org is no longer fit for purpose
Previous Message Jelte Fennema-Nio 2024-05-17 12:31:43 Re: commitfest.postgresql.org is no longer fit for purpose