Re: Why clearing the VM doesn't require registering vm buffer in wal record

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Melanie Plageman <melanieplageman(at)gmail(dot)com>
Cc: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Andres Freund <andres(at)anarazel(dot)de>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Subject: Re: Why clearing the VM doesn't require registering vm buffer in wal record
Date: 2026-07-15 20:10:59
Message-ID: CA+TgmoZyKK=whuOEtp6n8AHykhf6b=Jn4STbESJGu4VEVbEyGg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jul 15, 2026 at 3:34 PM Melanie Plageman
<melanieplageman(at)gmail(dot)com> wrote:
> Got it. For now I moved the push to the end of the function (after the
> if (!IPC::Run::run…) block). Then if pg_combinebackup fails, it prints
> right away but if it succeeds and a later assertion fails, those print
> at the end. I think END won't run if perl crashes -- maybe I don't
> need to solve for that, though?

If perl dumps core, that's not your problem.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2026-07-15 20:16:22 Re: walsummarizer can get stuck when switching timelines
Previous Message Melanie Plageman 2026-07-15 20:00:41 Re: Fix FSM range endpoint after relation extension