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 1l0FU7-0004fa-Kp for pgsql-admin@arkaria.postgresql.org; Fri, 15 Jan 2021 03:09:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1l0FU6-0005CE-If for pgsql-admin@arkaria.postgresql.org; Fri, 15 Jan 2021 03:09:10 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l0FU6-0005BP-Bi for pgsql-admin@lists.postgresql.org; Fri, 15 Jan 2021 03:09:10 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l0FU4-0004ez-9E for pgsql-admin@lists.postgresql.org; Fri, 15 Jan 2021 03:09:10 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 10F396ov1624858; Thu, 14 Jan 2021 22:09:06 -0500 From: Tom Lane To: S Bob cc: pgsql-admin@lists.postgresql.org Subject: Re: Odd config issue, cannot set log_min_duration_statement In-reply-to: References: <2a31bc9d-5c9b-b76e-083d-c4fb392f0834@quadratum-braccas.com> <1623237.1610677900@sss.pgh.pa.us> <1624198.1610679226@sss.pgh.pa.us> Comments: In-reply-to S Bob message dated "Thu, 14 Jan 2021 20:01:49 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1624856.1610680146.1@sss.pgh.pa.us> Date: Thu, 14 Jan 2021 22:09:06 -0500 Message-ID: <1624857.1610680146@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk S Bob writes: > On 1/14/21 7:53 PM, Tom Lane wrote: >> IIRC, that means you've applied a setting via ALTER USER, >> which'd override the default from the config file. > Yup, that's the last thing I tried: > postgres=# ALTER SYSTEM SET log_min_duration_statement = 0; But somewhere you did "ALTER *USER* yourself", and that's overriding the ALTER SYSTEM for your sessions. ALTER USER RESET should get rid of that. regards, tom lane