public inbox for [email protected]
help / color / mirror / Atom feedFrom: adherent postgres <[email protected]>
To: Chris Travers <[email protected]>
Cc: Chris Travers <[email protected]>
Cc: Bruce Momjian <[email protected]>
Cc: Aleksander Alekseev <[email protected]>
Cc: [email protected] <[email protected]>
Subject: =?gb2312?B?u9i4tDogQWRkIDY0LWJpdCBYSURzIGludG8gUG9zdGdyZVNRTCAxNQ==?=
Date: Fri, 9 Dec 2022 12:34:38 +0000
Message-ID: <TY0PR0101MB45861E76766D327D06FAACB08E1C9@TY0PR0101MB4586.apcprd01.prod.exchangelabs.com> (raw)
Hi Chris Travers
Robertmhaas said that the project Zheap is dead（https://twitter.com/andy_pavlo/status/1590703943176589312）, which means that we cannot use Zheap to deal with the issue of xid wraparound and dead tuples in tables. The dead tuple issue is not a big deal because I can still use pg_repack to handle, although pg_repack will cause wal log to increase dramatically and may take one or two days to handle a large table. During this time the database can be accessed by external users, but the xid wraparound will cause PostgreSQL to be down, which is a disaster for DBAs. Maybe you are not a DBA, or your are from a small country, Database system tps is very low, so xid32 is enough for your database system , Oracle's scn was also 32bits, however, Oracle realized the issue and changed scn to 64 bits. The transaction id in mysql is 48 bits. MySQL didn't fix the transaction id wraparound problem because they think that 48 bits is enough for the transaction id. This project has been running for almost 1 year and now it is coming to an end. I strongly disagree with your idea of stopping this patch, and I suspect you are a saboteur. I strongly disagree with your viewpoint, as it is not a fundamental way to solve the xid wraparound problem. The PostgreSQL community urgently needs developers who solve problems like this, not bury one' head in the sand
Best whish
________________________________
发件人: Peter Geoghegan <[email protected]>
发送时间: 2022年12月1日 0:35
收件人: Robert Haas <[email protected]>
抄送: Chris Travers <[email protected]>; Bruce Momjian <[email protected]>; Aleksander Alekseev <[email protected]>; [email protected] <[email protected]>; Chris Travers <[email protected]>; Fedor Sigaev <[email protected]>; Alexander Korotkov <[email protected]>; Konstantin Knizhnik <[email protected]>; Nikita Glukhov <[email protected]>; Yura Sokolov <[email protected]>; Maxim Orlov <[email protected]>; Pavel Borisov <[email protected]>; Simon Riggs <[email protected]>
主题: Re: Add 64-bit XIDs into PostgreSQL 15
On Wed, Nov 30, 2022 at 8:13 AM Robert Haas <[email protected]> wrote:
> I haven't checked the patches to see whether they look correct, and
> I'm concerned in particular about upgrade scenarios. But if there's a
> way we can get that part committed, I think it would be a clear win.
+1
--
Peter Geoghegan
view thread (6+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: =?gb2312?B?u9i4tDogQWRkIDY0LWJpdCBYSURzIGludG8gUG9zdGdyZVNRTCAxNQ==?=
In-Reply-To: <TY0PR0101MB45861E76766D327D06FAACB08E1C9@TY0PR0101MB4586.apcprd01.prod.exchangelabs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox