Re: Back-patch of: avoid multiple hard links to same WAL file after a crash - Mailing list pgsql-hackers

From Noah Misch
Subject Re: Back-patch of: avoid multiple hard links to same WAL file after a crash
Date
Msg-id 20250426230315.35.nmisch@google.com
Whole thread Raw
In response to Re: Back-patch of: avoid multiple hard links to same WAL file after a crash  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Fri, Apr 25, 2025 at 03:35:06PM -0400, Andres Freund wrote:
> On 2025-04-20 14:53:39 -0700, Noah Misch wrote:
> > The checkpoints and WAL creation took 30s, but archiving was only 20% done
> > (based on file name 00000001000000000000006D) at the 360s PGCTLTIMEOUT.
> 
> Huh.  That seems surprisingly slow, even for valgrind.  I guess it's one more
> example for why the single-threaded archiving approach sucks so badly :)

Yes!  I also didn't expect that v14/v13 would run much faster.

> I just changed the config to --trace-children=no. There already is a valgrind
> run in progress, so it won't be in effect for the next run.

Works for me.  I see that resolved things.



pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: pgsql: Add function to get memory context stats for processes
Next
From: David Rowley
Date:
Subject: Re: Get rid of integer divide in FAST_PATH_REL_GROUP() macro