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

postmaster

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Tom Lane authored
    Historically, VACUUM has just reported its new_rel_tuples estimate
    (the same thing it puts into pg_class.reltuples) to the stats collector.
    That number counts both live and dead-but-not-yet-reclaimable tuples.
    This behavior may once have been right, but modern versions of the
    pgstats code track live and dead tuple counts separately, so putting
    the total into n_live_tuples and zero into n_dead_tuples is surely
    pretty bogus.  Fix it to report live and dead tuple counts separately.
    
    This doesn't really do much for situations where updating transactions
    commit concurrently with a VACUUM scan (possibly causing double-counting or
    omission of the tuples they add or delete); but it's clearly an improvement
    over what we were doing before.
    
    Hari Babu, reviewed by Amit Kapila
    115f4141
    History
    Name Last commit Last update
    ..