Re: cleanup patches for incremental backup

Alexander Lakhin <exclusion@gmail.com>

From: Alexander Lakhin <exclusion@gmail.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Jakub Wartak <jakub.wartak@enterprisedb.com>, "Shinoda, Noriyoshi (HPE Services Japan - FSIP)" <noriyoshi.shinoda@hpe.com>
Date: 2024-01-13T18:00:00Z
Lists: pgsql-hackers

Attachments

Hello Robert,

12.01.2024 17:50, Robert Haas wrote:
> On Thu, Jan 11, 2024 at 8:00 PM Shinoda, Noriyoshi (HPE Services Japan
> - FSIP) <noriyoshi.shinoda@hpe.com> wrote:
>> Thank you for developing the new tool. I have attached a patch that corrects the spelling of the --individual option in the SGML file.
> Thanks, committed.

I've found one more typo in the sgml:
summarized_pid
And one in a comment:
sumamry

A trivial fix is attached.

Best regards,
Alexander

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Avoid overflow in MaybeRemoveOldWalSummaries().

  2. Revert "Temporary patch to help debug pg_walsummary test failures."

  3. Revise pg_walsummary's 002_blocks test to avoid spurious failures.

  4. Temporary patch to help debug pg_walsummary test failures.

  5. More documentation updates for incremental backup.

  6. Fix typos.

  7. Fix typo.

  8. Try to fix pg_walsummary buildfarm failures.

  9. Repair various defects in dc212340058b4e7ecfc5a7a81ec50e7a207bf288.

  10. Add new pg_walsummary tool.

  11. Add new function pg_get_wal_summarizer_state().

  12. Document WAL summarization information functions.