Re: cleanup patches for incremental backup
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Nathan Bossart <nathandbossart@gmail.com>
Cc: Alexander Lakhin <exclusion@gmail.com>, Matthias van de Meent <boekewurm+postgres@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2024-01-30T16:52:54Z
Lists: pgsql-hackers
Attachments
- v1-0001-Revise-pg_walsummary-s-002_blocks-test-to-avoid-s.patch (application/octet-stream) patch v1-0001
On Tue, Jan 30, 2024 at 10:51 AM Robert Haas <robertmhaas@gmail.com> wrote: > I think the solution here is to find a better way to wait for the > inserts to be summarized, one that actually does wait for that to > happen. Here's a patch for that. I now think a7097ca630a25dd2248229f21ebce4968d85d10a was actually misguided, and served only to mask some of the failures caused by waiting for the WAL summary file. -- Robert Haas EDB: http://www.enterprisedb.com
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Avoid overflow in MaybeRemoveOldWalSummaries().
- 80686761c49d 17.0 landed
-
Revert "Temporary patch to help debug pg_walsummary test failures."
- 2b520860c08a 17.0 landed
-
Revise pg_walsummary's 002_blocks test to avoid spurious failures.
- ea18eb7d6255 17.0 landed
-
Temporary patch to help debug pg_walsummary test failures.
- 5ddf99734777 17.0 landed
-
More documentation updates for incremental backup.
- 7b1dbf0a8d1d 17.0 landed
-
Fix typos.
- 237d01139b8a 17.0 landed
-
Fix typo.
- 882887e9b458 17.0 landed
-
Try to fix pg_walsummary buildfarm failures.
- a7097ca630a2 17.0 cited
-
Repair various defects in dc212340058b4e7ecfc5a7a81ec50e7a207bf288.
- 3d5c332a3d60 17.0 landed
-
Add new pg_walsummary tool.
- ee1bfd168390 17.0 landed
-
Add new function pg_get_wal_summarizer_state().
- d9ef650fca7b 17.0 landed
-
Document WAL summarization information functions.
- f896057e46b0 17.0 landed