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
    Tom Lane authored
    In the original coding of the log rotation stuff, we did not bother to make
    the truncation logic work for the very first rotation after postmaster
    start (or after a syslogger crash and restart).  It just always appended
    in that case.  It did not seem terribly important at the time, but we've
    recently had two separate complaints from people who expected it to work
    unsurprisingly.  (Both users tend to restart the postmaster about as often
    as a log rotation is configured to happen, which is maybe not typical use,
    but still...)  Since the initial log file is opened in the postmaster,
    fixing this requires passing down some more state to the syslogger child
    process.
    
    It's always been like this, so back-patch to all supported branches.
    b76356ac
    History
    Name Last commit Last update