aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/transam/xlogutils.c
diff options
context:
space:
mode:
authorDavid Rowley <drowley@postgresql.org>2023-04-07 12:47:10 +1200
committerDavid Rowley <drowley@postgresql.org>2023-04-07 12:47:10 +1200
commitae78cae3be627213528f2e08eb976d6906d754de (patch)
tree2a26745127fc1fa06d9890d6406a1280ad523705 /src/backend/access/transam/xlogutils.c
parent00d1e02be24987180115e371abaeb84738257ae2 (diff)
downloadpostgresql-ae78cae3be627213528f2e08eb976d6906d754de.tar.gz
postgresql-ae78cae3be627213528f2e08eb976d6906d754de.zip
Add --buffer-usage-limit option to vacuumdb
1cbbee033 added BUFFER_USAGE_LIMIT to the VACUUM and ANALYZE commands, so here we permit that option to be specified in vacuumdb. In passing, adjust the documents for vacuum_buffer_usage_limit and the BUFFER_USAGE_LIMIT VACUUM option to mention "kB" rather than "KB". Do the same for the ERROR message in ExecVacuum() and check_vacuum_buffer_usage_limit(). Without that we might tell a user that the valid minimum value is 128 KB only to reject that because we accept only "kB" and not "KB". Also, add a small reminder comment in vacuum.h to try to trigger the memory of anyone adding new fields to VacuumParams that they might want to consider if vacuumdb needs to grow a new option too. Author: Melanie Plageman Reviewed-by: Justin Pryzby Reviewed-by: David Rowley Discussion: https://postgr.es/m/ZAzTg3iEnubscvbf@telsasoft.com
Diffstat (limited to 'src/backend/access/transam/xlogutils.c')
0 files changed, 0 insertions, 0 deletions