pgsql: Prevent walsummarizer from getting stuck at a timeline switch.

Поиск
Список
Период
Сортировка
Искать

pgsql: Prevent walsummarizer from getting stuck at a timeline switch.

От:
Robert Haas <rhaas@postgresql.org>
Дата:
Prevent walsummarizer from getting stuck at a timeline switch.

As previously coded, walsummarizer only wants to read WAL from a file
where the TimeLineID in the filename exactly matches the TimeLineID being
summarized. But in some cases, when a timeline switch occurs, the WAL file
from the old timeline is not archived, because it's never completely
filled, so the only way to obtain the contents of that last partial
segment is to read from the first segment on the new timeline. Teach
WAL summarizer to do that, and add a test case to make sure that it
works.

Reported-by: Nick Ivanov 
Reviewed-by: Andrey Borodin 
Tested-by: Amit Kapila 
Reviewed-by: Srinath Reddy Sadipiralla 
Reviewed-by: Zhijie Hou 
Reviewed-by: Thom Brown 
Discussion: http://postgr.es/m/CA+Tgmobr27GpKDZx3_ezW2+C5_g18i+jSK3sGF_cR-_ESv5N5A@mail.gmail.com
Backpatch-through: 17

Branch
------
REL_18_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/18f0de6b885a017dfba620e0b9a5f42a1bc16d25

Modified Files
--------------
src/backend/postmaster/walsummarizer.c    | 173 +++++++++++++++++++++++++++---
src/bin/pg_walsummary/meson.build         |   1 +
src/bin/pg_walsummary/t/003_tli_switch.pl | 149 +++++++++++++++++++++++++
3 files changed, 309 insertions(+), 14 deletions(-)

FAQ