Re: Odd config issue, cannot set log_min_duration_statement - Mailing list pgsql-admin

From franklin ferreira de lima
Subject Re: Odd config issue, cannot set log_min_duration_statement
Date
Msg-id 6000ffd1.1c69fb81.f82a0.b9f5@mx.google.com
Whole thread Raw
In response to Odd config issue, cannot set log_min_duration_statement  (S Bob <sbob@quadratum-braccas.com>)
List pgsql-admin
Centro de educação integral 



Enviado do meu smartphone Samsung Galaxy.

-------- Mensagem original --------
De: Tom Lane <tgl@sss.pgh.pa.us>
Data: 14/01/21 23:31 (GMT-03:00)
Para: S Bob <sbob@quadratum-braccas.com>
Cc: pgsql-admin@lists.postgresql.org
Assunto: Re: Odd config issue, cannot set log_min_duration_statement

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


pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: Odd config issue, cannot set log_min_duration_statement
Next
From: Scott Ribe
Date:
Subject: Re: Odd config issue, cannot set log_min_duration_statement