Re: Error handling in after-startup shmem requests

From: Andres Freund <andres(at)anarazel(dot)de>
To: Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com>
Cc: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Error handling in after-startup shmem requests
Date: 2026-09-01 18:50:23
Message-ID: a4iyecm7rvykyfvui6shuyjwnvvccnwtnvvk2nia4d2vtcbcli@4yrz6hs2ex66
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2026-08-29 14:15:42 +0530, Ayush Tiwari wrote:
> On Sat, 29 Aug 2026 at 02:35, Andres Freund <andres(at)anarazel(dot)de> wrote:
> > On 2026-08-28 17:58:55 +0300, Heikki Linnakangas wrote:
> > > On 26/08/2026 15:44, Ayush Tiwari wrote:
> > > > I took a quick look and triggered the tests parallely.
> > > >
> > > > Patch looks good to me.
> > >
> > > Committed, thanks!
> >
> > This test reliably fails for me locally. I think it may be due to my system
> > having huge pages configured and the default of the huge_pages GUC being
> > try. When using huge pages, we round up the allocation, which increases the
> > reserve. Which then triggers the test to fail to fail, as the reserve is
> > bigger than 128kB.
> >
>
> Thanks for the report.
>
> The attached patch disables huge pages immediately before the allocation-
> failure phase. This keeps the test focused on recovery from an allocation
> failure rather than on the platform's shared memory segment rounding.

Thanks. Pushed.

Greetings,

Andres Freund

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2026-09-01 18:51:02 Re: Identifier downcase change for LATIN1, in v19
Previous Message Andrey Borodin 2026-09-01 18:49:41 Re: Allow ON CONFLICT DO UPDATE to return EXCLUDED values