Fix assertion when decrementing eager scanning success and failure counters.
Previously, we asserted that the eager scan's success and failure counters were positive before decrementing them. However, this assumption was incorrect, as it's possible that some blocks have already been eagerly scanned by the time eager scanning is disabled. This commit replaces the assertions with guards to handle this scenario gracefully. With this change, we continue to allow read-ahead operations by the read stream that exceed the success and failure caps. While there is a possibility that overruns will trigger eager scans of additional pages, this does not pose a practical concern as the overruns will not be substantial and remain within an acceptable range. Reviewed-by: Melanie Plageman <melanieplage...@gmail.com> Discussion: https://postgr.es/m/CAD21AoConf6tkVCv-=jhqjj56kysdwo4jg5+wqgt+ukskyo...@mail.gmail.com Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/4c08ecd1618e3c5da664ba24a4aa7052772c4616 Modified Files -------------- src/backend/access/heap/vacuumlazy.c | 29 +++++++++++++++++------------ 1 file changed, 17 insertions(+), 12 deletions(-)
