pgsql: Remove unneeded vacuum_delay_point from heap_vac_scan_get_next_b

From: Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Remove unneeded vacuum_delay_point from heap_vac_scan_get_next_b
Date: 2024-03-11 18:46:00
Message-ID: E1rjket-003IAI-U3@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Remove unneeded vacuum_delay_point from heap_vac_scan_get_next_block

heap_vac_scan_get_next_block() does relatively little work, so there
is no need to call vacuum_delay_point(). A future commit will call
heap_vac_scan_get_next_block() from a callback, and we would like to
avoid calling vacuum_delay_point() in that callback.

Author: Melanie Plageman
Discussion: https://postgr.es/m/CAAKRu_Yf3gvXGcCnqqfoq0Q8LX8UM-e-qbm_B1LeZh60f8WhWA%40mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/3d8652cd32846e4f9eaff9580858d281136bd0fd

Modified Files
--------------
src/backend/access/heap/vacuumlazy.c | 1 -
1 file changed, 1 deletion(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Jeff Davis 2024-03-11 19:26:55 Re: pgsql: Catalog changes preparing for builtin collation provider.
Previous Message Nathan Bossart 2024-03-11 18:13:37 pgsql: clusterdb: Allow specifying tables to process in all databases.