英文:
Postgresql settings not changing after editing postgresql.conf file. Postgresql 13. Debian 11
问题
以下是已翻译的内容:
根据经验,发现参数 log_min_duration_statement = 0
和 logging_collector = on
确实设置在 pg_settings 表中。但是,pg_settings 表中的参数不会对 postgresql.conf 中的更改作出反应。在更改 postgresql.conf 后,使用 systemctl restart postgresql
命令重新启动了 PostgreSQL。在 postgresql.conf 文件中,参数 logging_collector = off
。
英文:
Empirically, it was revealed that the parameters log_min_duration_statement = 0
and logging_collector = on
are indeed set in the pg_settings table. But the parameters in the pg_settings table do not react to changes in postgresql.conf. After changing postgresql.conf, postgresql restarted with the systemctl restart postgresql
command. In the postgresql.conf file parameter logging_collector = off
.
答案1
得分: 0
以下是已翻译的内容:
有一些简单的可能错误,你可能犯了以下错误:
-
编辑了错误的
postgresql.conf
文件 -
重新启动了错误的服务器
如果你可以排除这些解释,那么 postgresql.conf
中的设置必须在其他地方被覆盖了。通过以下方式找出覆盖设置的来源:
SELECT name, setting, source, sourcefile, sourceline
FROM pg_settings
WHERE name IN ('logging_collector', 'log_min_duration_statement');
最后三列告诉你设置的来源。
英文:
There are some simple possible mistakes that you could have made:
-
edit the wrong
postgresql.conf
-
restart the wrong server
If you can rule out these explanations, the setting from postgresql.conf
must have been overridden somewhere else. Find out where with
SELECT name, setting, source, sourcefile, sourceline
FROM pg_settings
WHERE name IN ('logging_collector', 'log_min_duration_statement');
The last three columns tell you where the setting originates.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库,让每个人都能够通过互相帮助和分享经验来进步。
评论