mirror of
https://github.com/postgres/postgres.git
synced 2025-10-22 14:32:25 +03:00
Revert "Add eager and lazy freezing strategies to VACUUM."
This reverts commit 4d41799261
. Broad
concerns about regressions caused by eager freezing strategy have been
raised. Whether or not these concerns can be worked through in any time
frame is far from certain.
Discussion: https://postgr.es/m/20230126004347.gepcmyenk2csxrri@awork3.anarazel.de
This commit is contained in:
@@ -222,9 +222,6 @@ typedef struct VacuumParams
|
||||
* use default */
|
||||
int multixact_freeze_table_age; /* multixact age at which to scan
|
||||
* whole table */
|
||||
int freeze_strategy_threshold; /* threshold to use eager
|
||||
* freezing, in megabytes, -1 to
|
||||
* use default */
|
||||
bool is_wraparound; /* force a for-wraparound vacuum */
|
||||
int log_min_duration; /* minimum execution threshold in ms at
|
||||
* which autovacuum is logged, -1 to use
|
||||
@@ -277,14 +274,6 @@ struct VacuumCutoffs
|
||||
*/
|
||||
TransactionId FreezeLimit;
|
||||
MultiXactId MultiXactCutoff;
|
||||
|
||||
/*
|
||||
* Eager freezing strategy is used whenever target rel's main fork size
|
||||
* exceeds freeze_strategy_threshold_pages. Otherwise lazy freezing
|
||||
* strategy is used. (Actually, there are exceptions. Non-permanent
|
||||
* tables always use eager freezing strategy.)
|
||||
*/
|
||||
BlockNumber freeze_strategy_threshold_pages;
|
||||
};
|
||||
|
||||
/*
|
||||
@@ -308,7 +297,6 @@ extern PGDLLIMPORT int vacuum_freeze_min_age;
|
||||
extern PGDLLIMPORT int vacuum_freeze_table_age;
|
||||
extern PGDLLIMPORT int vacuum_multixact_freeze_min_age;
|
||||
extern PGDLLIMPORT int vacuum_multixact_freeze_table_age;
|
||||
extern PGDLLIMPORT int vacuum_freeze_strategy_threshold;
|
||||
extern PGDLLIMPORT int vacuum_failsafe_age;
|
||||
extern PGDLLIMPORT int vacuum_multixact_failsafe_age;
|
||||
|
||||
|
Reference in New Issue
Block a user