Re: BUG #17757: Not honoring huge_pages setting during initdb causes DB crash in Kubernetes

From: Christophe Pettus <xof(at)thebuild(dot)com>
To: "Sisson, David" <David(dot)Sisson(at)dell(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #17757: Not honoring huge_pages setting during initdb causes DB crash in Kubernetes
Date: 2023-01-23 19:38:09
Message-ID: C0176E91-8B71-4CA2-9FCE-B27944040D6D@thebuild.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> On Jan 23, 2023, at 11:26, Sisson, David <David(dot)Sisson(at)dell(dot)com> wrote:
>
> I believe something should be done with PostgreSQL because we are configuring huge_pages = off in the standard "postgresql.conf" file.

We are? I believe the default is "huge_pages = try", not off.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Sisson, David 2023-01-23 19:51:14 RE: BUG #17757: Not honoring huge_pages setting during initdb causes DB crash in Kubernetes
Previous Message Sisson, David 2023-01-23 19:26:09 RE: BUG #17757: Not honoring huge_pages setting during initdb causes DB crash in Kubernetes