I've installed the Temboard tool (http://temboard.io/) to start monitoring my postgresql server. I've noticed that when I modify the postgresql.conf on the server and I restart it, the change is not taken into consideration. If I do it in the Temboard terminal it is. Is it normal? I was supposing that temboard should follow what is done in the postgresql.conf if I modify it on the server. Where temboard agent manages the server config?
Postgresql – Temboard: when monitoring a server modifying postgresql.conf on the server is not effective
monitoringpostgresql
Related Solutions
What you can do is to have below script stored on your server or make it as a stored procedure :
use below with sqlcmd
IF EXISTS ( SELECT 1
FROM MASTER.dbo.sysprocesses
WHERE program_name = N'SQLAgent - Generic Refresher')
BEGIN
SELECT @@SERVERNAME AS 'InstanceName', 1 AS 'SQLServerAgentRunning'
END
ELSE
BEGIN
EXEC msdb.dbo.sp_send_dbmail
@profile_name = 'databaseMail test profile', --<-- Change HERE !!
@recipients = 'databaseteam@somecompany.com', --<-- Change HERE !!
@body = 'Please check the status of SQL Agent. It is not running !',
@query = 'SELECT @@SERVERNAME AS [InstanceName], 0 AS [SQLServerAgentRunning]',
@subject = 'SQL Agent is not running',
@attach_query_result_as_file = 0 ; -- set it to 1 to receive as txt file attachment
END
What you can do to alleviate it :
Take a look at the postgresql.auto.conf file - it's populated if you changed it using alter system.
Also, make sure to restart the instance and not just reload it as this kind of change requires restart.
Related Question
- PostgreSQL Configuration – Modifying postgresql.conf Using pg_ctl
- PostgreSQL 9.5 – Won’t Start After Windows 10 Fall Update
- PostgreSQL – Resolving ‘postgresql.conf Not Found’ Issue
- PostgreSQL Logging – Impact of Logrotate on Log Files
- Postgresql – How should I configure the postgresql.conf file to backup the database once per hour
- PostgreSQL – Troubleshooting Server Restart Issues
- PostgreSQL V13 Master-Slave Replication on Window Server 2016 Not Replicating
Best Answer
Temboard presumably uses
ALTER SYSTEM, which on the server side, writes intopostgresql.auto.conf.The contents of
postgresql.auto.conftakes precedence over the contents ofpostgresql.conf, so if a setting is specified with both methods, the value inpostgresql.confis going to be ignored, no matter how you restart.To get back to the situation where the setting in
postgresql.confis not ignored, consider doingThen the next reload or restart should pick up the value from
postgresql.conf.