Re: Return pg_control from pg_backup_stop().

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Greg Burd <greg(at)burd(dot)me>
Cc: David Steele <david(at)pgbackrest(dot)org>, "Burd, Greg" <gregburd(at)amazon(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "hlinnaka(at)iki(dot)fi" <hlinnaka(at)iki(dot)fi>, "robertmhaas(at)gmail(dot)com" <robertmhaas(at)gmail(dot)com>, "andres(at)anarazel(dot)de" <andres(at)anarazel(dot)de>, "masao(dot)fujii(at)gmail(dot)com" <masao(dot)fujii(at)gmail(dot)com>, "solai(dot)cdac(at)gmail(dot)com" <solai(dot)cdac(at)gmail(dot)com>
Subject: Re: Return pg_control from pg_backup_stop().
Date: 2026-10-31 00:01:13
Message-ID: auUvyVF2hw4nbZdD@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Oct 30, 2026 at 04:04:13PM +0000, Greg Burd wrote:
> On Friday, October 30th, 2026 at 4:34 AM, David Steele <david(at)pgbackrest(dot)org> wrote:
>> I've attached a patch for be_lo_export(). Working around compiler bugs
>> is never fun but I'm not sure what choice we have.
>
> I've not reviewed the patch yet, but it is on my queue.

Thanks. Making sure that be_lo_export() can be faulty on SPARC and
also making sure that the palloc/pfree fixes it would be really
useful. I'm not sure that I'm going to spend cycles spawning an
instance just for this purpose. That does not feel like the most
useful use of time with everything that is spawning on the lists these
days.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Chao Li 2026-10-31 00:05:28 Re: Remove unused is_redo argument from pgstat_execute_transactional_drops()
Previous Message Tom Lane 2026-10-30 23:33:21 [PG19] Bogus errors for polymorphic plpython functions