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 1l0Ebv-0002uS-Iq for pgsql-admin@arkaria.postgresql.org; Fri, 15 Jan 2021 02:13: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 1l0Ebt-0007Og-UW for pgsql-admin@arkaria.postgresql.org; Fri, 15 Jan 2021 02:13:09 +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 1l0Ebt-0007OT-N0 for pgsql-admin@lists.postgresql.org; Fri, 15 Jan 2021 02:13:09 +0000 Received: from [64.147.123.21] (helo=wout5-smtp.messagingengine.com) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l0Ebr-0002gc-7G for pgsql-admin@lists.postgresql.org; Fri, 15 Jan 2021 02:13:08 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id CD6C91591; Thu, 14 Jan 2021 21:12:55 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Thu, 14 Jan 2021 21:12:56 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= quadratum-braccas.com; h=to:from:subject:message-id:date :mime-version:content-type; s=fm1; bh=PlOCo4v8rgKy2aXFMZqxxC4JGy NjQg380ty4DP2JABY=; b=Y3QD5TLVT0zRv6g6nul0ip3jt8S917PT9eHOAbinE1 eno466TGhvhUm9Is68TygfanLylKIMHcrq2wznsmxFMDE06dZuJ8yGwD2mDZorcm cwy1FaYBkH5YKXkzUtSRbAAQxoWjyvaOv7+TuIPaFb8CmhfVqMciPV62mVpL/Jfg wdFklDG5xaaDBwJAQ7Sqvd+Ih21yWKYyaZUlzpSeVYvZ/MyKE8knpdn7fsPrNxQS ShH3YNe4Yxrk7bRcOSetkY2tycySXeXCwvFFNsGEZQq/XgzL1WnwT3b1uO3+TRQ4 gv+p2WDqT+2JgpYMYfYUoYCBLzgYwIFoagqT+QXqOwgA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=PlOCo4v8rgKy2aXFMZqxxC4JGyNjQ g380ty4DP2JABY=; b=auwlzjoHyYgUp5S6VDBykzCq5jITe77UDI7h/bijCz+LZ 7tnkRXseEK2bGtMxocy91jtBzaO5zXLPV8UY4DvFRe7m5X1fufdd9R29l+TpkH0k 3q4vVScVJKhAnMiKSIfl3BAMd8cOm7fr3tdLREZCgIMGCdZDT4p72YS7G0J0u4KJ GIe7ZksRMuQbv4horGlEslx5yheELmuPxGldB23PkzvyO7XBo5YB4Vq3gObQhNJB h1V974849P0EK0A+WISld93Whw11xVhGf9rHUfe9Zkn+vecB5avKnC0EW/D7RvVf owmt8TViqncGNzR4vtjNFX6HuHvvvvfJ3V5ksJDxA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrtddugdegfecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepvffhuffkffgfgggtsegrtderredtfe ejnecuhfhrohhmpefuuceuohgsuceoshgsohgssehquhgrughrrghtuhhmqdgsrhgrtggt rghsrdgtohhmqeenucggtffrrghtthgvrhhnpeekleelhefggfegteeitdegiefgudfhte ejtdeuuedvheevleefkefgkeetjeffjeenucfkphephedtrddvgeefrdduhedtrdekuden ucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehssghosg esqhhurggurhgrthhumhdqsghrrggttggrshdrtghomh X-ME-Proxy: Received: from [10.16.0.101] (50-243-150-81-static.hfc.comcastbusiness.net [50.243.150.81]) by mail.messagingengine.com (Postfix) with ESMTPA id 1B875240057; Thu, 14 Jan 2021 21:12:55 -0500 (EST) To: pgsql-admin@lists.postgresql.org From: S Bob Subject: Odd config issue, cannot set log_min_duration_statement Message-ID: <2a31bc9d-5c9b-b76e-083d-c4fb392f0834@quadratum-braccas.com> Date: Thu, 14 Jan 2021 19:12:54 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------AA9CDC92603D169CE0B8552F" Content-Language: en-US X-Host-Lookup-Failed: Reverse DNS lookup failed for 64.147.123.21 (deferred) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is a multi-part message in MIME format. --------------AA9CDC92603D169CE0B8552F Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit All; I have a client running PostgreSQL v10 I set: log_min_duration_statement = 0 and restarted the cluster but if I connect via psql and check it's still disabled postgres=# show log_min_duration_statement ;  log_min_duration_statement ----------------------------  -1 (1 row) I tried an alter system, now if I cat the auto.conf file i see: $ cat postgresql.auto.conf # Do not edit this file manually! # It will be overwritten by the ALTER SYSTEM command. log_min_duration_statement = '0' However even after another restart It's still disabled: postgres=# show log_min_duration_statement ;  log_min_duration_statement ----------------------------  -1 (1 row) I grep'ed for the setting in the config file just in case: $ grep log_min_duration_statement postgresql.conf log_min_duration_statement = 0          # -1 is disabled, 0 logs all statements I'm stumped... Thoughts? Thanks in advance --------------AA9CDC92603D169CE0B8552F Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

All;


I have a client running PostgreSQL v10


I set:

log_min_duration_statement = 0

and restarted the cluster but if I connect via psql and check it's still disabled


postgres=# show log_min_duration_statement ;
 log_min_duration_statement
----------------------------
 -1
(1 row)


I tried an alter system, now if I cat the auto.conf file i see:


$ cat postgresql.auto.conf
# Do not edit this file manually!
# It will be overwritten by the ALTER SYSTEM command.
log_min_duration_statement = '0'


However even after another restart It's still disabled:


postgres=# show log_min_duration_statement ;
 log_min_duration_statement
----------------------------
 -1
(1 row)


I grep'ed for the setting in the config file just in case:

$ grep log_min_duration_statement postgresql.conf
log_min_duration_statement = 0          # -1 is disabled, 0 logs all statements


I'm stumped... Thoughts?


Thanks in advance



--------------AA9CDC92603D169CE0B8552F--