回复: Add 64-bit XIDs into PostgreSQL 15

From: adherent postgres <adherent_postgres(at)hotmail(dot)com>
To: Chris Travers <chris(dot)travers(at)gmail(dot)com>
Cc: Chris Travers <chris(at)orioledata(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Aleksander Alekseev <aleksander(at)timescale(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: 回复: Add 64-bit XIDs into PostgreSQL 15
Date: 2022-12-09 12:34:38
Message-ID: TY0PR0101MB45861E76766D327D06FAACB08E1C9@TY0PR0101MB4586.apcprd01.prod.exchangelabs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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 <pg(at)bowt(dot)ie>
发送时间: 2022年12月1日 0:35
收件人: Robert Haas <robertmhaas(at)gmail(dot)com>
抄送: Chris Travers <chris(at)orioledata(dot)com>; Bruce Momjian <bruce(at)momjian(dot)us>; Aleksander Alekseev <aleksander(at)timescale(dot)com>; pgsql-hackers(at)lists(dot)postgresql(dot)org <pgsql-hackers(at)lists(dot)postgresql(dot)org>; Chris Travers <chris(dot)travers(at)gmail(dot)com>; Fedor Sigaev <teodor(at)sigaev(dot)ru>; Alexander Korotkov <aekorotkov(at)gmail(dot)com>; Konstantin Knizhnik <knizhnik(at)garret(dot)ru>; Nikita Glukhov <n(dot)gluhov(at)postgrespro(dot)ru>; Yura Sokolov <y(dot)sokolov(at)postgrespro(dot)ru>; Maxim Orlov <orlovmg(at)gmail(dot)com>; Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com>; Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com>
主题: Re: Add 64-bit XIDs into PostgreSQL 15

On Wed, Nov 30, 2022 at 8:13 AM Robert Haas <robertmhaas(at)gmail(dot)com> 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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Juan José Santamaría Flecha 2022-12-09 12:48:53 Re: WIN32 pg_import_system_collations
Previous Message Alexander Korotkov 2022-12-09 12:30:14 Re: Allow placeholders in ALTER ROLE w/o superuser