Thread: 回复: Add 64-bit XIDs into PostgreSQL 15

Hi adherent,

>      Robertmhaas said that the project Zheap is dead（https://twitter.com/andy_pavlo/status/1590703943176589312）,
whichmeans that we cannot use Zheap to deal with the issue of xid wraparound and dead tuples in tables. The dead tuple
issueis not a big deal because I can still use pg_repack to handle, although pg_repack will cause wal log to increase
dramaticallyand may take one or two days to handle a large table. During this time the database can be accessed by
externalusers, but the xid wraparound will cause PostgreSQL to be down, which is a disaster for DBAs. Maybe you are not
aDBA, 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
mysqlis 48 bits. MySQL didn't fix the transaction id wraparound problem because they think that 48 bits is enough for
thetransaction id. This project has been running for almost 1 year and now it is coming to an end. I strongly disagree
withyour idea of stopping this patch, and I suspect you are a saboteur. I strongly disagree with your viewpoint, as it
isnot a fundamental way to solve the xid wraparound problem. The PostgreSQL community urgently needs developers who
solveproblems like this, not bury one' head in the sand 

This is not uncommon for people on the mailing list to have
disagreements. This is part of the process, we all are looking for
consensus. It's true that different people have different use cases in
mind and different backgrounds as well. It doesn't mean these use
cases are wrong and/or the experience is irrelevant and/or the
received feedback should be just discarded.

Although I also expressed my disagreement with Chris before, let's not
assume any bad intent and especially sabotage as you put it. (Unless
you have a strong proof of this of course which I doubt you have.) We
want all kinds of feedback to be welcomed here. I'm sure our goal here
is mutual, to make PostgreSQL even better than it is now. The only
problem is that the definition of "better" varies sometimes.

I see you believe that 64-bit XIDs are going to be useful. That's
great! Tell us more about your case and how the patch is going to help
with it. Also, maybe you could test your load with the applied
patchset and tell us whether it makes things better or worse?
Personally I would love hearing this from you.

--
Best regards,
Aleksander Alekseev

Hi, Adherent!

On Fri, 9 Dec 2022 at 17:54, adherent postgres
<adherent_postgres@hotmail.com> wrote:
>
> Hi Aleksander Alekseev
>  I think the xids 32bit transformation project has been dragged on for too long. Huawei's openGauss referenced this
patchto implement xids 64bit, and Postgrespro also implemented xids 64bit, which is enough to prove that their worries
areredundant.I think postgresql has no reason not to implement xid 64 bit. What about your opinion? 

I agree it's high time to commit 64xids into PostgreSQL.

If you can do your review of the whole proposed patchset or only the
part that is likely to be committed earlier [1] it would help a lot!
I'd recommend beginning with the last version of the patch in thread
[1]. First, it is easier. Also, this review is going to be useful
sooner and will help a committer on January commitfest a lot.
[1]: https://www.postgresql.org/message-id/CAFiTN-uudj2PY8GsUzFtLYFpBoq_rKegW3On_8ZHdxB1mVv3-A%40mail.gmail.com

Regards,
Pavel Borisov,
Supabase