Re: Return pg_control from pg_backup_stop().

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: David Steele <david(at)pgbackrest(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, solai v <solai(dot)cdac(at)gmail(dot)com>, hofstetter(at)jomasoft(dot)ch
Subject: Re: Return pg_control from pg_backup_stop().
Date: 2026-10-29 00:48:55
Message-ID: auKX96FoUmFGkgfn@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Oct 28, 2026 at 09:26:41AM -0700, Noah Misch wrote:
> I won't be able to help with that directly, but:
>
> - thorntail is cfarm202.cfarm.net; accounts are available:
> https://portal.cfarm.net/users/new/
>
> - If a newer buildfarm client would collect a stack trace here, I'm happy to
> upgrade.

Could it be possible to send the result of an objdump -d on
perform_base_backup() perhaps, before and after the fact? That should
offer the glimpse of a hint, at least.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2026-10-29 00:50:46 Re: Return pg_control from pg_backup_stop().
Previous Message Masahiko Sawada 2026-10-29 00:39:23 Re: [PG19] pg_upgrade --check passes, then the upgrade fails