| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | David Steele <david(at)pgbackrest(dot)org>, 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> |
| Subject: | Re: Return pg_control from pg_backup_stop(). |
| Date: | 2026-10-29 08:14:43 |
| Message-ID: | auMAc2PTDDNnk1gv@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Oct 29, 2026 at 09:50:46AM +0900, Michael Paquier wrote:
> I unfortunately do not have a better idea after sleeping on it, so I
> have applied this palloc0/pfree solution. Now I'll go light a candle
> to make the buildfarm gods kinder to me.
billbug has just switched back to green on HEAD after two successive
failures, so it looks like the stack sizing was the right guess:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=billbug&dt=2026-10-29%2004%3A00%3A03
So something is going on here. How could we rule out if this is
something on the Postgres side with SPARC?
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bertrand Drouvot | 2026-10-29 08:23:13 | Re: Report buffer access strategies in EXPLAIN |
| Previous Message | Michael Paquier | 2026-10-29 08:11:26 | Re: pgsql: Set HEAP_XMAX_INVALID for tuples updated by aborted subtransacti |