From: Tatsuo Ishii <ishii@postgresql.org>
To: pgpool-committers@lists.postgresql.org
Subject: pgpool: Doc: fix track_table_mutation memory figures and eviction descr
Date: Wed, 30 Sep 2026 02:20:28 +0000
Message-ID: <E1xBjvo-0000000DvYZ-2p0S@gothos.postgresql.org> (raw)
Doc: fix track_table_mutation memory figures and eviction description.
The track table mutation documentation understated the shared memory the
feature requires and described its eviction order incorrectly.
TrackTableMutationEntry is 56 bytes, not the documented 40: it holds two
struct timeval fields (16 bytes each on LP64), two ints, a uint32, an int
and a bool, which pad to 56. With the default track_table_mutation_table_size
of 2048 that is ~112 KB for the entries, plus ~4 KB for the default 1024
hash buckets, so the feature needs ~116 KB rather than ~80 KB. The
4096-table example needs ~228 KB, not ~160 KB. The bucket array was not
accounted for at all before; it is now mentioned explicitly.
The docs also stated that the oldest entries are evicted when the map is
full. table_map_insert() actually scans from bucket zero and evicts the
head of the first non-empty bucket, so the eviction order follows the hash
bucket layout and not the write time. Describe what the code does, and
note that expired entries are reclaimed opportunistically, so a live entry
is only evicted when more than track_table_mutation_table_size tables are
written inside one TTL window.
The Japanese document patch by Tatsuo Ishii.
Author: Nadav Shatz <nadav@tailorbrands.com>
Reviewed-by: Tatsuo Ishii <ishii@postgresql.org>
Discussion: https://www.postgresql.org/message-id/CACeKOO1v6%2BKiK-qns_37zCz7YYxJ6Zi_xKaLAuQcjkYQcjQu2Q%40mail.g...
Backpatch-through: master only
Branch
------
master
Details
-------
https://git.postgresql.org/gitweb?p=pgpool2.git;a=commitdiff;h=17352edb15faf64752a22fd4f1491cf3f268c...
Modified Files
--------------
doc.ja/src/sgml/loadbalance.sgml | 17 ++++++++++-------
doc/src/sgml/loadbalance.sgml | 23 +++++++++++++++--------
2 files changed, 25 insertions(+), 15 deletions(-)
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgpool-committers@postgresql.org
Cc: ishii@postgresql.org
Subject: Re: pgpool: Doc: fix track_table_mutation memory figures and eviction descr
In-Reply-To: <E1xBjvo-0000000DvYZ-2p0S@gothos.postgresql.org>
References: <E1xBjvo-0000000DvYZ-2p0S@gothos.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox