pg.ddx.io pgsql-committers@postgresql.org mailing list archive
help / color / mirror / Atom feedpgsql: Fix limit block handling in pg_wal_summary_contents().
2+ messages / 1 participants
[nested] [flat]
* pgsql: Fix limit block handling in pg_wal_summary_contents().
@ 2024-07-09 00:30 Fujii Masao <fujii@postgresql.org>
0 siblings, 0 replies; 2+ messages in thread
From: Fujii Masao @ 2024-07-09 00:30 UTC (permalink / raw)
To: pgsql-committers@lists.postgresql.org
Fix limit block handling in pg_wal_summary_contents().
Previously, pg_wal_summary_contents() had two issues,
causing discrepancies between pg_wal_summary_contents()
and the pg_walsummary command on the same WAL summary file:
(1) It did not emit the limit block when that's the only data for
a particular relation fork.
(2) It emitted the same limit block multiple times if the list of
block numbers was long enough.
This commit fixes these issues.
Backpatch to v17 where pg_wal_summary_contents() was added.
Author: Fujii Masao
Reviewed-by: Robert Haas
Discussion: https://postgr.es/m/90980ee6-2da6-42f6-a7b0-b7bae62ae279@oss.nttdata.com
Branch
------
REL_17_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/ab4129091ccc15c3e899878e8bd6733577f83bba
Modified Files
--------------
src/backend/backup/walsummaryfuncs.c | 34 +++++++++++++++++-----------------
1 file changed, 17 insertions(+), 17 deletions(-)
^ permalink raw reply [nested|flat] 2+ messages in thread
* pgsql: Fix limit block handling in pg_wal_summary_contents().
@ 2024-07-09 00:30 Fujii Masao <fujii@postgresql.org>
0 siblings, 0 replies; 2+ messages in thread
From: Fujii Masao @ 2024-07-09 00:30 UTC (permalink / raw)
To: pgsql-committers@lists.postgresql.org
Fix limit block handling in pg_wal_summary_contents().
Previously, pg_wal_summary_contents() had two issues,
causing discrepancies between pg_wal_summary_contents()
and the pg_walsummary command on the same WAL summary file:
(1) It did not emit the limit block when that's the only data for
a particular relation fork.
(2) It emitted the same limit block multiple times if the list of
block numbers was long enough.
This commit fixes these issues.
Backpatch to v17 where pg_wal_summary_contents() was added.
Author: Fujii Masao
Reviewed-by: Robert Haas
Discussion: https://postgr.es/m/90980ee6-2da6-42f6-a7b0-b7bae62ae279@oss.nttdata.com
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/c8d5d6c78af4a55c5c36e2fa8e73d1f2b2e9d777
Modified Files
--------------
src/backend/backup/walsummaryfuncs.c | 34 +++++++++++++++++-----------------
1 file changed, 17 insertions(+), 17 deletions(-)
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2024-07-09 00:30 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2024-07-09 00:30 pgsql: Fix limit block handling in pg_wal_summary_contents(). Fujii Masao <fujii@postgresql.org>
2024-07-09 00:30 pgsql: Fix limit block handling in pg_wal_summary_contents(). Fujii Masao <fujii@postgresql.org>
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