pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Tomas Vondra <tomas.vondra@enterprisedb.com>
Cc: david_sisson@dell.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17757: Not honoring huge_pages setting during initdb causes DB crash in Kubernetes
Date: Sat, 21 Jan 2023 19:08:01 -0500
Message-ID: <1116926.1674346081@sss.pgh.pa.us> (raw)
In-Reply-To: <20230121234501.b7b2skgbdw73ujvh@awork3.anarazel.de>
References: <17757-dbdfc1f1c954a6db@postgresql.org>
	<4ce40288-5b88-f9fb-ea11-fc932c61472b@enterprisedb.com>
	<20230121232922.juo7t3fhaso7qh3s@awork3.anarazel.de>
	<1113361.1674343983@sss.pgh.pa.us>
	<20230121234501.b7b2skgbdw73ujvh@awork3.anarazel.de>

Andres Freund <andres@anarazel.de> writes:
> Perhaps we should add an option to force MAP_POPULATE being used? I'm fairly
> certain that'd avoid the SIGBUS in this case. And it'd make sense to ensure
> that we can actually use the memory in initdb.

> Unfortunately it's not unproblematic to use it in general, because with large
> shared_buffers values it can be quite slow, because the kernel initializes the
> memory in a single thread. I've seen ~3GB/s on multi-socket machines.

Hmm ... but if we can't use it by default, we're still back to the
problem of needing a way to tell initdb to do things differently.
I'd just as soon keep that to "set huge_pages = off" rather than
inventing whole new things.

			regards, tom lane





view thread (25+ messages)  latest in thread

Message-ID: <1116926.1674346081@sss.pgh.pa.us>
Permalink:  ../1116926.1674346081@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/1116926.1674346081@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-bugs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, andres@anarazel.de, tomas.vondra@enterprisedb.com, david_sisson@dell.com
  Subject: Re: BUG #17757: Not honoring huge_pages setting during initdb causes DB crash in Kubernetes
  In-Reply-To: <1116926.1674346081@sss.pgh.pa.us>
  References: <17757-dbdfc1f1c954a6db@postgresql.org> <4ce40288-5b88-f9fb-ea11-fc932c61472b@enterprisedb.com> <20230121232922.juo7t3fhaso7qh3s@awork3.anarazel.de> <1113361.1674343983@sss.pgh.pa.us> <20230121234501.b7b2skgbdw73ujvh@awork3.anarazel.de> <1116926.1674346081@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox