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 1nUFvQ-0004rH-8f for pgsql-hackers@arkaria.postgresql.org; Tue, 15 Mar 2022 22:45:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nUFuQ-0002th-Ce for pgsql-hackers@arkaria.postgresql.org; Tue, 15 Mar 2022 22:44:54 +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 1nUFuQ-0002tY-1i for pgsql-hackers@lists.postgresql.org; Tue, 15 Mar 2022 22:44:54 +0000 Received: from mail-pl1-x633.google.com ([2607:f8b0:4864:20::633]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nUFuG-0000Mm-IY for pgsql-hackers@postgresql.org; Tue, 15 Mar 2022 22:44:52 +0000 Received: by mail-pl1-x633.google.com with SMTP id e13so352718plh.3 for ; Tue, 15 Mar 2022 15:44:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=qS7OP8y8IEzNamZdncUUeT8upjDhVBIadWUhyRmj2Dg=; b=CG1yljdPTsue0KUc6Zcqrf7jP39xrQAwDprHMvtYR0OSLZTwPJqwKGbH28THGVMB3U f666rmSPJzBCFayyejNQTkP8FrDGgHwVJMoPrrGLxwJX6DCLF4eytbeP+8SgCY81ebsy Nf/ll+LwlSZGzaeoffZFDdP+RrRS5q5rXpnjU5rJ149iII0Cb1ZyVpokCl9dknoYQxKx 4lMz0nzayzywGwFLkSvjkW+vDp9IYnNwOsOAvcL7hZm/YoUc80FCla5ORAGsHyuR+5sj CVhW56GFP3fco40R4OeR+iQecbRZAL56a/2VXwTHlpLXl7TdSLRrCSu0NqS0s+lm2YIF RfJg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=qS7OP8y8IEzNamZdncUUeT8upjDhVBIadWUhyRmj2Dg=; b=5btygZMIS30A9OADl4Jhfnm3nR1+XlQH9ZDoGLFJ8uoGzEUe6HRff9pB772MQn2nWg O8/vglOWxRrnZ5xkqgBpsgnMICaZYgVbXm2nxAnUwtpvaT7+mzwQCHp3zE0jcAUtYEYc Qb36g6zEG+xtl9HhqTZMB6LE2ZTFApAhX048iYKgNTmwFgtUIfo4+nxj07PPyn+KDZ2H ArlG5KuFSL2Cv3g3z/6V/VZ8PjyUd4kkUJkwCaRFZ3kbICMsejfAltrsyqZUJaWH2yQH e1YLs0qyJb/qAzT+Dac8s/fUMj+bBiOXHmBNPGTyio85V4ni7VLuE+t2Zd6hjXSrCzRh lZ9Q== X-Gm-Message-State: AOAM530Ka4nrIepz1NLL3wivyDVirZh+yLSVkGMoPfkV+aic97VbgQWT cy5hOjUPOIG6FUnxT2OafP0= X-Google-Smtp-Source: ABdhPJx6jRfhH54/gsHWYncBYAABYzBfD1m06S5xKU2AqAVQ0EQgz09MctORI2J9sMwQ3DWFJoZDMA== X-Received: by 2002:a17:90a:5291:b0:1bb:ef4d:947d with SMTP id w17-20020a17090a529100b001bbef4d947dmr7035752pjh.243.1647384282479; Tue, 15 Mar 2022 15:44:42 -0700 (PDT) Received: from nathanxps13 ([50.54.155.70]) by smtp.gmail.com with ESMTPSA id d4-20020aa78e44000000b004f6aaa184c9sm142706pfr.71.2022.03.15.15.44.41 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 15 Mar 2022 15:44:41 -0700 (PDT) Date: Tue, 15 Mar 2022 15:44:39 -0700 From: Nathan Bossart To: Magnus Hagander Cc: Michael Paquier , "Bossart, Nathan" , Fujii Masao , Justin Pryzby , Andres Freund , Mark Dilger , Don Seiler , "pgsql-hackers@postgresql.org" Subject: Re: Estimating HugePages Requirements? Message-ID: <20220315224439.GA1133771@nathanxps13> References: <4cc5b434-b174-9aae-197b-737db6cac4e3@oss.nttdata.com> <6AE0285D-0917-4C05-B6AA-4AEDD2FCBA52@amazon.com> <20220314173417.GA1020555@nathanxps13> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="82I3+IH0IqGh5yIs" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --82I3+IH0IqGh5yIs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Mar 15, 2022 at 11:02:37PM +0100, Magnus Hagander wrote: > I think we're talking about two different things here. > > I think the "avoid extra logging" would be worth seeing if we can > address for 15. A simple approach could be to just set log_min_messages to PANIC before exiting. I've attached a patch for this. With this patch, we'll still see a FATAL if we try to use 'postgres -C' for a runtime-computed GUC on a running server, and there will be no extra output as long as the user sets log_min_messages to INFO or higher (i.e., not a DEBUG* value). For comparison, 'postgres -C' for a non-runtime-computed GUC does not emit extra output as long as the user sets log_min_messages to DEBUG2 or higher. > The "able to run on a live cluster" seems a lot bigger and more scary > and not 15 material. +1 -- Nathan Bossart Amazon Web Services: https://aws.amazon.com --82I3+IH0IqGh5yIs Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="v2-0001-don-t-emit-shutdown-messages-for-postgres-C-with-.patch"