abb*_*ood 5 postgresql logging rds
我重新启动了实例和一切,我得到了这个新的日志文件:
在 error/postgres.log 中,我只有这个:
2018-03-13 12:39:38 UTC::@:[28236]:WARNING: unrecognized configuration parameter "rds.logical_replication"
2018-03-13 12:39:38 UTC::@:[28236]:LOG: redirecting log output to logging collector process
2018-03-13 12:39:38 UTC::@:[28236]:HINT: Future log output will appear in directory "/rdsdbdata/log/error".
2018-03-13 13:07:39 UTC::@:[11128]:WARNING: unrecognized configuration parameter "rds.logical_replication"
2018-03-13 13:07:39 UTC::@:[11128]:LOG: redirecting log output to logging collector process
2018-03-13 13:07:39 UTC::@:[11128]:HINT: Future log output will appear in directory "/rdsdbdata/log/error".
2018-03-13 14:13:53 UTC::@:[14981]:WARNING: unrecognized configuration parameter "rds.logical_replication"
2018-03-13 14:13:53 UTC::@:[14981]:LOG: redirecting log output to logging collector process
2018-03-13 14:13:53 UTC::@:[14981]:HINT: Future log output will appear in directory "/rdsdbdata/log/error".
----------------------- END OF LOG ----------------------
Run Code Online (Sandbox Code Playgroud)
一件令人担忧的事情是,我从未收到此消息,因为文档说我应该在应用新更改后:
2013-11-05 16:48:56 UTC::@:[2952]:LOG: received SIGHUP, reloading configuration files
2013-11-05 16:48:56 UTC::@:[2952]:LOG: parameter "log_min_duration_statement" changed to "1"
Run Code Online (Sandbox Code Playgroud)
任何想法我做错了什么?
回应此评论:
forge=> select name,setting,source from pg_settings where name like 'log_%';
name | setting | source
-----------------------------+----------------------------+--------------------
log_autovacuum_min_duration | -1 | default
log_checkpoints | on | configuration file
log_connections | off | default
log_destination | stderr | configuration file
log_directory | /rdsdbdata/log/error | configuration file
log_disconnections | off | default
log_duration | off | default
log_error_verbosity | default | default
log_executor_stats | off | default
log_file_mode | 0644 | configuration file
log_filename | postgresql.log.%Y-%m-%d-%H | configuration file
log_hostname | on | configuration file
log_line_prefix | %t:%r:%u@%d:[%p]: | configuration file
log_lock_waits | off | default
log_min_duration_statement | 1 | configuration file
log_min_error_statement | error | default
log_min_messages | warning | default
log_parser_stats | off | default
log_planner_stats | off | default
log_replication_commands | off | default
log_rotation_age | 60 | configuration file
log_rotation_size | 10240 | default
log_statement | all | configuration file
log_statement_stats | off | default
log_temp_files | -1 | default
log_timezone | UTC | configuration file
log_truncate_on_rotation | off | configuration file
logging_collector | on | configuration file
Run Code Online (Sandbox Code Playgroud)
与下面的正确答案相同,我得到了 RDS 支持的回复并得到了这个:
我想让您知道,在应用参数组更改后,我可以看到为您的实例生成的日志文件。此外,我还可以看到这些日志文件的大小越来越大。应用修改参数组并重启后生成的日志文件(附加参数组在 2018-03-13 12:35:58 UTC 并在 2018-03-13 12:39:33 UTC 重启),如如下:
Run Code Online (Sandbox Code Playgroud)File Name Date and Time of generation Size -------------------------------------------------------------------------------------------- error/postgresql.log.2018-03-13-12 2018-03-13T12:59:56+00:00 592550 error/postgresql.log.2018-03-13-13 2018-03-13T13:59:53+00:00 2258196 error/postgresql.log.2018-03-13-14 2018-03-13T15:00:00+00:00 2761617 error/postgresql.log.2018-03-13-15 2018-03-13T15:59:03+00:00 1000738 error/postgresql.log.2018-03-13-16 2018-03-13T16:59:02+00:00 582653 error/postgresql.log.2018-03-13-17 2018-03-13T17:59:01+00:00 111647 error/postgresql.log.2018-03-13-18 2018-03-13T18:59:02+00:00 66102 error/postgresql.log.2018-03-13-19 2018-03-13T19:59:02+00:00 45318
文档似乎有些不一致/过时。当我今天早上更改参数组并重新启动时,我得到了同样奇怪的错误/postgres.log 文件,内容相同。
不知道这是否适合您,但对我来说这只是以愚蠢的顺序对日志进行排序。我刷新,按“上次写入(降序)”排序,弹出实际最新的日志。