Currently, PostgreSQL sends log entries to syslog; entries are then stored in /var/log/messages.
Plan is to create a separate log.
Should be configured for dbserver-pgsql role:
- syslog configuration
- newsyslog to create the log and handle the rotation
Description
Description
Related Objects
Related Objects
Event Timeline
dereckson created this task.
Comment ActionsIn T2185#33876, @dereckson wrote:Each test run produces this:
Nov 11 02:29:33 windriver postgres[63389]: [19-1] 2025-11-11 02:29:33.804 UTC [63389] ERROR: relation "nonexisting" does not exist at character 13 Nov 11 02:29:33 windriver postgres[63389]: [19-2] 2025-11-11 02:29:33.804 UTC [63389] STATEMENT: DELETE FROM nonexisting Nov 11 02:29:34 windriver postgres[63402]: [19-1] 2025-11-11 02:29:34.181 UTC [63402] ERROR: relation "nonexisting" does not exist at character 15 Nov 11 02:29:34 windriver postgres[63402]: [19-2] 2025-11-11 02:29:34.181 UTC [63402] STATEMENT: SELECT * FROM nonexisting Nov 11 02:29:34 windriver postgres[63403]: [19-1] 2025-11-11 02:29:34.209 UTC [63403] ERROR: relation "nonexisting" does not exist at character 15 Nov 11 02:29:34 windriver postgres[63403]: [19-2] 2025-11-11 02:29:34.209 UTC [63403] STATEMENT: SELECT * FROM nonexisting Nov 11 02:29:34 windriver postgres[63408]: [19-1] 2025-11-11 02:29:34.357 UTC [63408] ERROR: relation "not_existing_table" does not exist Nov 11 02:29:34 windriver postgres[63408]: [19-2] 2025-11-11 02:29:34.357 UTC [63408] STATEMENT: TRUNCATE not_existing_table Nov 11 02:29:34 windriver postgres[63409]: [19-1] 2025-11-11 02:29:34.385 UTC [63409] ERROR: relation "not_existing" does not exist Nov 11 02:29:34 windriver postgres[63409]: [19-2] 2025-11-11 02:29:34.385 UTC [63409] STATEMENT: TRUNCATE not_existing Nov 11 02:29:34 windriver postgres[63416]: [19-1] 2025-11-11 02:29:34.591 UTC [63416] FATAL: password authentication failed for user "notexisting" Nov 11 02:29:34 windriver postgres[63416]: [19-2] 2025-11-11 02:29:34.591 UTC [63416] DETAIL: Role "notexisting" does not exist. Nov 11 02:29:34 windriver postgres[63416]: [19-3] Connection matched pg_hba.conf line 22: "host all all 127.0.0.1/32 scram-sha-256"I guess we could avoid to post PostgreSQL logs directly in /var/log/messages.