Skip to content
Snippets Groups Projects
Select Git revision
  • benchmark-tools
  • postgres-lambda
  • master default
  • REL9_4_25
  • REL9_5_20
  • REL9_6_16
  • REL_10_11
  • REL_11_6
  • REL_12_1
  • REL_12_0
  • REL_12_RC1
  • REL_12_BETA4
  • REL9_4_24
  • REL9_5_19
  • REL9_6_15
  • REL_10_10
  • REL_11_5
  • REL_12_BETA3
  • REL9_4_23
  • REL9_5_18
  • REL9_6_14
  • REL_10_9
  • REL_11_4
23 results

postgres-lambda-diff

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Fujii Masao authored
    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.
    4ad2a548
    History
    Name Last commit Last update