| From: | Ryoga Yoshida <bt23yoshidar(at)oss(dot)nttdata(dot)com> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Bug fix in vacuumdb --buffer-usage-limit xxx -Z |
| Date: | 2023-09-21 01:44:49 |
| Message-ID: | 08930c0b541700a5264e5fbf3a685f5a@oss.nttdata.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
When --buffer-usage-limit option is specified, vacuumdb issues VACUUM or
VACUUM ANALYZE command with BUFFER_USAGE_LIMIT option. Also if
--buffer-usage-limit and -Z options are specified, vacuumdb should issue
ANALYZE command with BUFFER_USAGE_LIMIT option. But it does not. That
is, vacuumdb -Z seems to fail to handle --buffer-usage-limit option.
This seems a bug.
You can see my patch in the attached file and how it works by adding -e
option in vacuumdb.
Ryoga Yoshida
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-bug-fix-in-vacuumdb-buffer-usage-limit-Z.patch | text/x-diff | 593 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kuwamura Masaki | 2023-09-21 01:53:09 | Re: bug fix and documentation improvement about vacuumdb |
| Previous Message | Amit Langote | 2023-09-21 01:06:58 | Re: Memory consumed by child SpecialJoinInfo in partitionwise join planning |