diff options
| author | David Rowley <drowley@postgresql.org> | 2023-04-03 19:19:45 +1200 |
|---|---|---|
| committer | David Rowley <drowley@postgresql.org> | 2023-04-03 19:19:45 +1200 |
| commit | 32fbe0239b03d868744758d5809eaf74f19c924d (patch) | |
| tree | f1d425957033e3ea7c25fe6c9c64d928ffd12409 /src/backend/executor/nodeModifyTable.c | |
| parent | 1980d3585e3c7fce74b811ca8d77733036cae76c (diff) | |
| download | postgresql-32fbe0239b03d868744758d5809eaf74f19c924d.tar.gz postgresql-32fbe0239b03d868744758d5809eaf74f19c924d.zip | |
Only make buffer strategy for vacuum when it's likely needed
VACUUM FULL and VACUUM ONLY_DATABASE_STATS will not use the vacuum
strategy ring created in vacuum(), so don't waste effort making it in
those cases.
There are other conceivable cases where the buffer strategy also won't be
used, but those are probably less common and not worth troubling over too
much. For example VACUUM (PROCESS_MAIN false, PROCESS_TOAST false).
There are other cases too, but many of these are only discovered once
inside vacuum_rel().
Author: Melanie Plageman
Reviewed-by: David Rowley
Discussion: https://postgr.es/m/CAAKRu_ZLRuzkM3zKogiZAz2hUony37yLY4aaLb8fPf8fgqs5Og@mail.gmail.com
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions