| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, postgresql(at)taljaren(dot)se, pgsql-bugs(at)lists(dot)postgresql(dot)org, Peter Geoghegan <pg(at)bowt(dot)ie> |
| Subject: | Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue) |
| Date: | 2022-12-18 02:23:27 |
| Message-ID: | 06770AA8-58E8-44C8-A0FF-558289897DDC@thebuild.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
> In order to control all that, rather than a hardcoded rule, could it
> be as simple as introducing an option like vacuumdb --batch=N
> defaulting to 1 to let users control the number of relations grouped
> in a single command with a round robin distribution for each slot?
My first reaction to that is: Is it possible to explain to a DBA what N should be for a particular cluster?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2022-12-18 23:55:00 | Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue) |
| Previous Message | Michael Paquier | 2022-12-18 02:21:47 | Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2022-12-18 03:14:23 | Rework of collation code, extensibility |
| Previous Message | Michael Paquier | 2022-12-18 02:21:47 | Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue) |