diff options
| author | David Rowley <drowley@postgresql.org> | 2023-04-16 12:05:34 +1200 |
|---|---|---|
| committer | David Rowley <drowley@postgresql.org> | 2023-04-16 12:05:34 +1200 |
| commit | c0235013c13b0adc9e7f1998ff5700e26ecdbd1f (patch) | |
| tree | 998ba080dcd9c6c6e000038f4094fcea39f2641f /src/backend/executor/nodeAgg.c | |
| parent | 064eb89e83ea0f59426c92906329f1e6c423dfa4 (diff) | |
| download | postgresql-c0235013c13b0adc9e7f1998ff5700e26ecdbd1f.tar.gz postgresql-c0235013c13b0adc9e7f1998ff5700e26ecdbd1f.zip | |
Improve VACUUM/ANALYZE BUFFER_USAGE_LIMIT docs
This addresses various deficiencies in the documentation for VACUUM and
ANALYZE's BUFFER_USEAGE_LIMIT docs.
Here we declare "size" in the syntax synopsis for VACUUM and ANALYZE's
BUFFER_USAGE_LIMIT option and then define exactly what values can be
specified for it in the section for that below.
Also, fix the incorrect ordering of vacuumdb options both in the documents
and in vacuumdb's --help output. These should be in alphabetical order.
In passing also add the minimum/maximum range for the BUFFER_USAGE_LIMIT
option. These will also serve as example values that can be modified and
used.
Reported-by: Peter Eisentraut
Discussion: https://postgr.es/m/16845cb1-b228-e157-f293-5892bced9253@enterprisedb.com
Diffstat (limited to 'src/backend/executor/nodeAgg.c')
0 files changed, 0 insertions, 0 deletions