pgsql: Revert "Add single-item cache when looking at topmost XID of a s

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Revert "Add single-item cache when looking at topmost XID of a s
Date: 2022-05-28 06:21:07
Message-ID: E1nupow-001VdA-M4@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Revert "Add single-item cache when looking at topmost XID of a subtrans XID"

This reverts commit 06f5295 as per issues with this approach, both in
terms of efficiency impact and stability. First, contrary to the
single-item cache for transaction IDs in transam.c, the cache may finish
by not be hit for a long time, and without an invalidation mechanism to
clear it, it would cause inconsistent results on wraparound for
example. Second, the use of SubTransGetTopmostTransaction() for the
caching has a limited impact on performance. SubTransGetParent() could
have more impact, though the benchmarking of the single-item approach
still needs to be proved, particularly under the conditions where SLRU
lookups are stressed in parallel with overflowed snapshots (aka more
than 64 subxids generated, for example).

After discussion with Andres Freund.

Discussion: https://postgr.es/m/20220524235250.gtt3uu5zktfkr4hv@alap3.anarazel.de

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/b4529005fd387e863bfa9eb863629b1183c0449c

Modified Files
--------------
src/backend/access/transam/subtrans.c | 18 ------------------
1 file changed, 18 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Andres Freund 2022-05-28 20:13:45 pgsql: Align stats_fetch_consistency definition with guc.c default.
Previous Message Michael Paquier 2022-05-28 03:13:40 pgsql: Handle NULL for short descriptions of custom GUC variables