Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1q6CAL-00059d-Dl for pgsql-novice@arkaria.postgresql.org; Mon, 05 Jun 2023 15:30:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1q6CAK-0004tb-98 for pgsql-novice@arkaria.postgresql.org; Mon, 05 Jun 2023 15:30:40 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1q6CAK-0004qE-09 for pgsql-novice@lists.postgresql.org; Mon, 05 Jun 2023 15:30:40 +0000 Received: from sender11-op-o11.zoho.eu ([31.186.226.225]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1q6CAG-000Mkc-Qk for pgsql-novice@lists.postgresql.org; Mon, 05 Jun 2023 15:30:38 +0000 ARC-Seal: i=1; a=rsa-sha256; t=1685979033; cv=none; d=zohomail.eu; s=zohoarc; b=OpyKiBUlt1hC6jmG/+RQQxp0blgKlrQXsAXd6noj/8DNmStHNQOsA9qBBRWcFRpN2PTGGmyB9d6v/szfGEzSN3FkkU6BJVczIIYwDMst5FDetjm3pUAMy7L1rGd6H/pC4fQQla7KipOAXK2xnZQJRdQFXY9eneaXLGnK71nJ4Tk= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.eu; s=zohoarc; t=1685979033; h=Content-Type:Content-Transfer-Encoding:Date:From:MIME-Version:Message-ID:Subject:To; bh=EYwg80bST33CxC/RYFZhzvL+XeijuSVP3P23ouNIIsc=; b=dPttDqubB6/xTPWyMCee9UgHK+D7zSkD5LFL9n9yaoaF+ZE2H5FItN9vmhMnugKyXhLkO3T/heoDMV9QykvJmEIsxX062mclNaQXuHcZjXmiDHo97A9xxGS0arZu1NHY37Jktp79C8dvCOEsMIIxQytAFtu8tdWhXuIGjS7qzXg= ARC-Authentication-Results: i=1; mx.zohomail.eu; dkim=pass header.i=trallnag.com; spf=pass smtp.mailfrom=tim@trallnag.com; dmarc=pass header.from= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1685979033; s=zmail; d=trallnag.com; i=tim@trallnag.com; h=Date:Date:From:From:To:To:Message-ID:In-Reply-To:Subject:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-Id:Reply-To:Cc; bh=EYwg80bST33CxC/RYFZhzvL+XeijuSVP3P23ouNIIsc=; b=SLEIQXGb6eHz+ETJbHfZ4vGIlNZ/QxjsTPd+8go3xN9xB7+BQeAIeKPg3wCNqsu/ Gyyok8OjDOUjDHM8qP68Y82M08MSljQigDc4IGJd49HKw6maHKFmNAebd+YVteCiqed 1JidCy0ExbdPeLCR5xFw64c39sVpuoWb7YgJUFi0= Received: from mail.zoho.eu by mx.zoho.eu with SMTP id 168597903285338.632196644148394; Mon, 5 Jun 2023 17:30:32 +0200 (CEST) Date: Mon, 05 Jun 2023 17:30:32 +0200 From: Tim Schwenke To: "Pgsql Novice" Message-ID: <1888c2e6d08.f41d0c1610286.4206746953200644373@trallnag.com> In-Reply-To: Subject: Will PostgreSQL use normal and huge pages at the same time? MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Importance: Medium User-Agent: Zoho Mail X-Mailer: Zoho Mail List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hello, the default in PostgreSQL is "try" (use if available). But what does this mean? 1. Will it only use huge pages if everything it needs fits into them? 2. Or will it first use huge pages and then use normal pages once no huge page is available anymore? Regards Tim