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

From Tomas Vondra
Subject Re: Refactoring postmaster's code to cleanup after child exit
Date
Msg-id acba60cc-b7e2-40fd-ba37-891fc3e0d2b9@vondra.me
Whole thread Raw
In response to Re: Refactoring postmaster's code to cleanup after child exit  (Andres Freund <andres@anarazel.de>)
Responses Re: Refactoring postmaster's code to cleanup after child exit
List pgsql-hackers
On 3/7/25 16:49, Andres Freund wrote:
> 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.
> 

Yes, the v2 fixes that too. I got confused by the message suggesting

  ... this pump stuff is all about getting better error messages
  on a test failure. It doesn't help with the original issue.

which made me believe the tests will still fail, so I haven't tried the
patches before. But that doesn't seem to be the case.


regards

-- 
Tomas Vondra



pgsql-hackers by date:

Previous
From: Nikolay Shaplov
Date:
Subject: Minor rework of ALTER TABLE SET RelOptions code
Next
From: Jacob Champion
Date:
Subject: Re: [PATCH] pg_stat_activity: make slow/hanging authentication more visible