aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor
diff options
context:
space:
mode:
authorAlvaro Herrera <alvherre@alvh.no-ip.org>2022-11-22 10:56:07 +0100
committerAlvaro Herrera <alvherre@alvh.no-ip.org>2022-11-22 10:56:07 +0100
commit0557e1770230fe5ca855fdf45bb297bd38a9ec1b (patch)
tree4a39cf6e28e8cc6216c3c514a728fb6ec2ddecb5 /src/backend/executor
parent92daeca45df6551dd85f92f7369eaa57a35fb8a9 (diff)
downloadpostgresql-0557e1770230fe5ca855fdf45bb297bd38a9ec1b.tar.gz
postgresql-0557e1770230fe5ca855fdf45bb297bd38a9ec1b.zip
Ignore invalidated slots while computing oldest catalog Xmin
Once a logical slot has acquired a catalog_xmin, it doesn't let go of it, even when invalidated by exceeding the max_slot_wal_keep_size, which means that dead catalog tuples are not removed by vacuum anymore since the point is invalidated, until the slot is dropped. This could be catastrophic if catalog churn is high. Change the computation of Xmin to ignore invalidated slots, to prevent dead rows from accumulating. Backpatch to 13, where slot invalidation appeared. Author: Sirisha Chamarthi <sirichamarthi22@gmail.com> Reviewed-by: Ashutosh Bapat <ashutosh.bapat.oss@gmail.com> Discussion: https://postgr.es/m/CAKrAKeUEDeqquN9vwzNeG-CN8wuVsfRYbeOUV9qKO_RHok=j+g@mail.gmail.com
Diffstat (limited to 'src/backend/executor')
0 files changed, 0 insertions, 0 deletions