diff options
author | David Rowley <drowley@postgresql.org> | 2023-04-06 15:44:52 +1200 |
---|---|---|
committer | David Rowley <drowley@postgresql.org> | 2023-04-06 15:44:52 +1200 |
commit | b9b125b9c14381c4d04a446e335bb2da5f602596 (patch) | |
tree | f162a5dbeca3bb9ec0de3720a25320d48960215e /contrib/postgres_fdw/sql/postgres_fdw.sql | |
parent | acab1b0914e426d28789731f50f5964dd4d2f054 (diff) | |
download | postgresql-b9b125b9c14381c4d04a446e335bb2da5f602596.tar.gz postgresql-b9b125b9c14381c4d04a446e335bb2da5f602596.zip |
Move various prechecks from vacuum() into ExecVacuum()
vacuum() is used for both the VACUUM command and for autovacuum. There
were many prechecks being done inside vacuum() that were just not relevant
to autovacuum. Let's move the bulk of these into ExecVacuum() so that
they're only executed when running the VACUUM command. This removes a
small amount of overhead when autovacuum vacuums a table.
While we are at it, allocate VACUUM's BufferAccessStrategy in ExecVacuum()
and pass it into vacuum() instead of expecting vacuum() to make it if it's
not already made by the calling function. To make this work, we need to
create the vacuum memory context slightly earlier, so we now need to pass
that down to vacuum() so that it's available for use in other memory
allocations.
Author: Melanie Plageman
Reviewed-by: David Rowley
Discussion: https://postgr.es/m/20230405211534.4skgskbilnxqrmxg@awork3.anarazel.de
Diffstat (limited to 'contrib/postgres_fdw/sql/postgres_fdw.sql')
0 files changed, 0 insertions, 0 deletions