| From: | S Bob <sbob(at)quadratum-braccas(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Odd config issue, cannot set log_min_duration_statement |
| Date: | 2021-01-15 03:01:49 |
| Message-ID: | aafc6974-65b7-2891-0966-88f5fd83a423@quadratum-braccas.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On 1/14/21 7:53 PM, Tom Lane wrote:
> S Bob <sbob(at)quadratum-braccas(dot)com> writes:
>> On 1/14/21 7:31 PM, Tom Lane wrote:
>>> Hmm, that should have worked. What do you see in
>>> select * from pg_settings where name = 'log_min_duration_statement';
>> source | user
> IIRC, that means you've applied a setting via ALTER USER,
> which'd override the default from the config file.
>
> regards, tom lane
Yup, that's the last thing I tried:
postgres=# ALTER SYSTEM SET log_min_duration_statement = 0;
and it added the entry in the postgresql.auto.conf file:
$ cat postgresql.auto.conf
# Do not edit this file manually!
# It will be overwritten by the ALTER SYSTEM command.
log_min_duration_statement = '0'
But... it's still -1, even after another restart
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-01-15 03:09:06 | Re: Odd config issue, cannot set log_min_duration_statement |
| Previous Message | Tom Lane | 2021-01-15 02:53:46 | Re: Odd config issue, cannot set log_min_duration_statement |