From: Tom Lane <tgl@sss.pgh.pa.us>
To: S Bob <sbob@quadratum-braccas.com>
cc: pgsql-admin@lists.postgresql.org
Subject: Re: Odd config issue, cannot set log_min_duration_statement
In-reply-to: <2a31bc9d-5c9b-b76e-083d-c4fb392f0834@quadratum-braccas.com>
References: <2a31bc9d-5c9b-b76e-083d-c4fb392f0834@quadratum-braccas.com>
Comments: In-reply-to S Bob <sbob@quadratum-braccas.com>
	message dated "Thu, 14 Jan 2021 19:12:54 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1623236.1610677900.1@sss.pgh.pa.us>
Date: Thu, 14 Jan 2021 21:31:40 -0500
Message-ID: <1623237.1610677900@sss.pgh.pa.us>
Precedence: bulk

S Bob <sbob@quadratum-braccas.com> writes:
> I set:
> log_min_duration_statement = 0
> and restarted the cluster but if I connect via psql and check it's still 
> disabled

If you just did "SET" then it'd only affect the current session.

> 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'

Hmm, that should have worked.  What do you see in

select * from pg_settings where name = 'log_min_duration_statement';

(the "source..." columns are important here)

			regards, tom lane