Обсуждение: [GENERAL] Postgres 9.6.2 and pg_log

​I don't see "log_rotation_age" and/or "log_rotation_size" here [1] and at least one needs to be set in order to enable actual rotation; the "truncate" option simply tells PostgreSQL what to do when encountering a file with the same name during the rotation process.​

log_rotation_age apparently has under-documented intelligence since I would expect a server that starts up mid-hour and uses a 60 minute rotation to rotate mid-hour as well so the log would contain 1 hours worth of data but the leading hours would be different.  The examples in log_truncate_on_rotation indicate that this isn't the case.  I have not tested reality or read the source.

​Um...you're reporting a very outdated 9.2 release in the supposed copy-paste job above but claiming 9.6.2 ...

[1] https://www.postgresql.org/docs/9.6/static/runtime-config-logging.html#RUNTIME-CONFIG-LOGGING-WHERE

Thanks, David,

The lines log_rotation_age and log_rotation_size are commented, and currently are:

#log_rotation_age = 1d                                 # Automatic rotation of logfiles will

                                                                                # happen after that time.  0 disables.

#log_rotation_size = 10MB                          # Automatic rotation of logfiles will

                                                                                # happen after that much log output.

                                                                                # 0 disables.

I see from your reference article that the log_rotation_age is now in minutes, and I will adjust that to 1440 (1 day). I don’t know where the “1d” came from. I know it used to be like this in earlier versions.

Mark Watson

​I don't see "log_rotation_age" and/or "log_rotation_size" here [1] and at least one needs to be set in order to enable actual rotation; the "truncate" option simply tells PostgreSQL what to do when encountering a file with the same name during the rotation process.​

log_rotation_age apparently has under-documented intelligence since I would expect a server that starts up mid-hour and uses a 60 minute rotation to rotate mid-hour as well so the log would contain 1 hours worth of data but the leading hours would be different.  The examples in log_truncate_on_rotation indicate that this isn't the case.  I have not tested reality or read the source.

​Um...you're reporting a very outdated 9.2 release in the supposed copy-paste job above but claiming 9.6.2 ...

[1] https://www.postgresql.org/docs/9.6/static/runtime-config-logging.html#RUNTIME-CONFIG-LOGGING-WHERE

Sorry about the version; I queried SELECT version() in pgAdmin4 and did not copy/paste the results. It is version 9.6.2.

​https://www.postgresql.org/docs/9.6/static/config-setting.html

​I think the actual missing, and (just checked) defaulted off, parameter is "logging_collector"

I have (copy/paste) :

log_destination = 'stderr'                             # Valid values are combinations of

                                                                                # stderr, csvlog, syslog, and eventlog,

                                                                                # depending on platform.  csvlog

                                                                                # requires logging_collector to be on.

# This is used when logging to stderr:

logging_collector = on                    # Enable capturing of stderr and csvlog

                                                                                # into log files. Required to be on for

                                                                                # csvlogs.

                                                                                # (change requires restart)

Mark Watson

​I'm out of ideas...

Not to worry. This week I’m uninstalling and reinstalling postgres 9.6. I’ll do some tests and let this list know.

Mark Watson