Add GUC to enable logging of replication commands

Enterprise / PostgreSQL - Fujii Masao [postgresql.org] - 12 September 2014 12:55 UTC

Previously replication commands like IDENTIFY_COMMAND were not logged even when log_statements is set to all. Some users who want to audit all types of statements were not satisfied with this situation. To address the problem, this commit adds new GUC log_replication_commands. If it's enabled, all replication commands are logged in the server log.

There are many ways to allow us to enable that logging. For example, we can extend log_statement so that replication commands are logged when it's set to all. But per discussion in the community, we reached the consensus to add separate GUC for that.

Reviewed by Ian Barwick, Robert Haas and Heikki Linnakangas.

4ad2a54 Add GUC to enable logging of replication commands.
doc/src/sgml/config.sgml | 16 ++++++++++++++++
doc/src/sgml/protocol.sgml | 2 ++
src/backend/replication/walsender.c | 11 +++++++++--
src/backend/utils/misc/guc.c | 9 +++++++++
src/backend/utils/misc/postgresql.conf.sample | 1 +
src/include/replication/walsender.h | 1 +
6 files changed, 38 insertions(+), 2 deletions(-)

Upstream: git.postgresql.org


  • Share