Re: Refactoring postmaster's code to cleanup after child exit - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Refactoring postmaster's code to cleanup after child exit
Date
Msg-id gqlpysgqqalst5yu6jtjh2n24etl5c2s4ypmu5gxnz3dwx637g@3dc5wo32tzv2
Whole thread Raw
In response to Re: Refactoring postmaster's code to cleanup after child exit  (Tomas Vondra <tomas@vondra.me>)
Responses Re: Refactoring postmaster's code to cleanup after child exit
List pgsql-hackers
Hi,

On 2025-03-07 16:25:09 +0100, Tomas Vondra wrote:
> FWIW I keep running into this (and skink seems unhappy too). I ended up
> just adding a sleep(1), right before
> 
> push(@sessions, background_psql_as_user('regress_superuser'));
> 
> and that makes it work on all my machines (including rpi5).

Can you confirm that the fix attached to my prior email suffices to address
the issue on your machine too?  I'm planning to push the fixes soon.

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Melanie Plageman
Date:
Subject: Re: Trigger more frequent autovacuums
Next
From: "Euler Taveira"
Date:
Subject: Re: Separate GUC for replication origins