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
    Robert Haas authored
    The old message was at DEBUG2, so typically it didn't show up in the
    log at all.  As a result, in most cases where autovacuum was canceled,
    the only information that was logged was the table being vacuumed,
    with no indication as to what problem caused the cancel.  Crank up
    the level to LOG and add some more details to assist with debugging.
    
    Back-patch all the way, per discussion on pgsql-hackers.
    a5bca248
    History
    Name Last commit Last update