| Type: | bool |
| Default: | off |
| Context: | superuser |
| Restart: | false |
| Since: | 9.5 |
Causes each replication command to be logged in the server log. See protocol-replication for more information about replication command. The default value is off. Only superusers and users with the appropriate SET privilege can change this setting.
Recommendations
… assuming you're monitoring replication status, which you should.
On StackOverflow
On pgsql-hackers
- Re: add log messages when replication slots become active and inactive (was Re: Is it worth adding ReplicationSlot active_pid to ReplicationSlotPersistentData?)
- Re: Is it worth adding ReplicationSlot active_pid to ReplicationSlotPersistentData?
- Re: fix stats_fetch_consistency value in postgresql.conf.sample
- add log messages when replication slots become active and inactive (was Re: Is it worth adding ReplicationSlot active_pid to ReplicationSlotPersistentData?)
- Re: [PATCH] New default role allowing to change per-role/database settings