Re: Add 64-bit XIDs into PostgreSQL 15

eal xid64-patch code once will perform pruning with repairFragmentation=false, and subsequently will perform Heap/INSERT+INIT. But maybe this contrived code will help us to replay the problem and to create specific TAP-test. Best regards, Evgeny Voropaev. From 650a90692a6f601057be145c7d62474462d

Re: Elimination of the repetitive code at the SLRU bootstrap functions.

Álvaro, thank you for pushing, attention and final editing of the patch! I got your recommendations and requirements. I will take them into account at a next patch. Andrey, Alexander thank you for your proposals, attention, advice, and review! Best regards, Evgeny Voropaev, Tantor Labs, LLC.

Re: Elimination of the repetitive code at the SLRU bootstrap functions.

Álvaro, Andrey, Alexander, hello! Since the master branch became the PG19dev and PG18 is now stable, I have directed this patch into PG19. Could we continue with it now? Álvaro, should I rename the SimpleLruZeroPageExt function? Best regards, Evgeny Voropaev. On 14.03.2025 21:43, Evgeny

Re: Add 64-bit XIDs into PostgreSQL 15

> What exactly would break if we did perform `heap_page_prune_execute` > with NO fragmentation repair during `heap_page_prepare_for_xid`? Correction into the last question: What exactly would break if we did invoke `heap_page_prune_execute` with `repairFragmentation=true` during performing of `

Re: Add 64-bit XIDs into PostgreSQL 15

execute` without a fragmentation during the preparation of a page for xid? What exactly would break if we did perform `heap_page_prune_execute` with NO fragmentation repair during `heap_page_prepare_for_xid`? Best regards, Evgeny Voropaev, Tantor Labs, LLC.

Re: Elimination of the repetitive code at the SLRU bootstrap functions.

een reverted to one Álvaro has proposed at first (XLogSimpleInsert). Patch looks even better - it reduce code by 180 lines. Best regards, Evgeny Voropaev.From a324f639627e2128ec64156453e97a7b1b8b420a Mon Sep 17 00:00:00 2001 From: Evgeny Voropaev Date: Wed, 12 Mar 2025 22:35:19 +0800 Subject: [PA

Re: Elimination of the repetitive code at the SLRU bootstrap functions.

f this function would better belong to SLRU than common XLog stuff. In accordance with Álvaro's proposal, we want to enclose this function in the "xloginsert.c" module. Best regards, Evgeny Voropaev.From 8c9aa484dc96cdf23c7fa524d88d67ce3c4cc6fc Mon Sep 17 00:00:00 2001 From: Evgeny Vo

Re: Elimination of the repetitive code at the SLRU bootstrap functions.

ntical to v4, except for the version number increment, which helps prevent duplicate attachment names in this thread. Best regards, Evgeny Voropaev.From 885c15ba379da4fd5f0dd71ee4dc9b5e31108d6f Mon Sep 17 00:00:00 2001 From: Evgeny Voropaev Date: Sun, 23 Feb 2025 23:19:19 +0800 Subject: [PATCH v5] E

Re: Elimination of the repetitive code at the SLRU bootstrap functions.

Hello Hackers! Álvaro, Andrey, Aleksander! We have not been discussing anything in the thread for the past ten days. Can we mark this thread as "Ready for Merge" or should I improve something in the patch. If I should, I am ready to do it. Looking forward to your feedback. Evgeny Voropaev.

Re: Elimination of the repetitive code at the SLRU bootstrap functions.

deletion now. comments are formatted as well. > sometimes I read source from bottom to top Probably, we all should profess this approach! Best regards, Evgeny Voropaev, Tantor Labs LLC. From 885c15ba379da4fd5f0dd71ee4dc9b5e31108d6f Mon Sep 17 00:00:00 2001 From: Evgeny Voropaev Date: Su

Re: Elimination of the repetitive code at the SLRU bootstrap functions.

. * * SimpleLruZeroPage performs: * 2. nullifying. */From de4621460b1b63fb3cbc78095af31e1e6b565dd2 Mon Sep 17 00:00:00 2001 From: Evgeny Voropaev Date: Tue, 18 Feb 2025 15:48:12 +0800 Subject: [PATCH v3] Elimination of the repetitive code at the SLRU bootstrapping and nullifying functions. The

Re: Elimination of the repetitive code at the SLRU bootstrap functions.

-dc69-4c3e-968f-a822ae0937b5%40gmail.com). The corrected patch version implementing these proposals is attached. Best regards, Evgeny Voropaev, Tantor Labs LLC. From a5a29cdbb37834bfcd23cd22db90a78a7db43d18 Mon Sep 17 00:00:00 2001 From: Evgeny Voropaev Date: Fri, 14 Feb 2025 14:03:01 +0800 Sub

Elimination of the repetitive code at the SLRU bootstrap functions.

realm of bootstrapping SLRU. Best regards, Evgeny Voropaev, Tantor Labs LLC.From 62762bf4a86af76d845755e41f46714d2b41bbe4 Mon Sep 17 00:00:00 2001 From: Evgeny Voropaev Date: Thu, 13 Feb 2025 12:43:20 +0800 Subject: [PATCH v1] Elimination of the repetitive code at the SLRU bootstrap functions

Re: Add 64-bit XIDs into PostgreSQL 15

Hi Evgeny      xid64 path split several threads ,The current one should be this:(https://www.postgresql.org/message-id/flat/CACG=ezawg7_nt-8ey4akv2w9lculthhknwcawmbgeetnjrj...@mail.gmail.com) ,We can do some tests on path so that  can merge earlier Thanks Hello Wenhui! Thank you for pointing

Re: [PATCH] Support Int64 GUCs

Hi hackers! Upgraded the "Int64 GUC" patch in order to conform to f3f06b13308e3 updates. Rebased and tested upon the current master (3f9b9621766). The patch is still needed to be up to date as a part of the xid64 solution. Best regards, Evgeny Voropaev, TantorLabs,

Re: [PATCH] Support Int64 GUCs

Hi hackers! Upgraded the "Int64 GUC" patch in order to conform to f3f06b13308e3 updates. Rebased and tested upon the current master (3f9b9621766). The patch is still needed to be up to date as a part of the xid64 solution. Best regards, Evgeny Voropaev, TantorLabs, LLC.

Can Execute commands for different portals interleave?

Greetings! The question (a short version): is it possible for a client to send two selects in the same transaction using the extended query protocol (without declaring cursors) and pull rows simultaneously by means of interleaving portal names and restricting fetch size in Execute commands. The

Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view?

The following review has been posted through the commitfest application: make installcheck-world: tested, passed Implements feature: tested, passed Spec compliant: tested, passed Documentation:tested, passed HI! patch is look good for me. The new status of this patch

Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view?

What reason to use pg_atomic_uint64? In docs: occured - > occurred