Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: postgresql-cfbot/postgresql
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: cf/5777~1
Choose a base ref
...
head repository: postgresql-cfbot/postgresql
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: cf/5777
Choose a head ref
  • 2 commits
  • 5 files changed
  • 2 contributors

Commits on May 31, 2025

  1. Fix reltuples stats after VACUUM FULL and CLUSTER 

    The tableam API's function for clustering a table, used by both
CLUSTER and VACUUM FULL, returns the number of non-removable tuples in
a num_tuples variable. This number includes dead tuples that cannot be
removed because they are still visible to concurrent
transactions. Previously, num_tuples was used to update
pg_class.reltuples, but this could lead to widely misleading numbers
if many tuples had been deleted or updated concurrently with ongoing
transactions. The fix is to not include the recently dead tuples.

It should be noted that this issue only occurred on tables that didn't
have any indexes, since the reindexing that happens as part of the
cluster code also updates reltuples, but using the more accurate
number based on currently visible tuples.
    @erimatnor
    erimatnor authored and Commitfest Bot committed May 31, 2025
    Configuration menu
    Copy the full SHA
    15d6ec1 View commit details
    Browse the repository at this point in the history

  2. [CF 5777] v1 - Correct reltuples stats after VACUUM FULL and CLUSTER 

    This branch was automatically generated by a robot using patches from an
email thread registered at:

https://commitfest.postgresql.org/patch/5777

The branch will be overwritten each time a new patch version is posted to
the thread, and also periodically to check for bitrot caused by changes
on the master branch.

Patch(es): https://www.postgresql.org/message-id/CACAa4V+vUyKwkqs8O_dqR736YOZoKaGQJFQZikAB8WSYyFzbrg@mail.gmail.com
Author(s): Erik Nordström
    Commitfest Bot committed May 31, 2025
    Configuration menu
    Copy the full SHA
    a838895 View commit details
    Browse the repository at this point in the history
Loading