Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue)

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Christophe Pettus <xof(at)thebuild(dot)com>
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-19 03:21:26
Message-ID: Y5/YtnCO8GNW9svE@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Sat, Dec 17, 2022 at 06:23:27PM -0800, Christophe Pettus wrote:
> My first reaction to that is: Is it possible to explain to a DBA
> what N should be for a particular cluster?

Assuming that we can come up with a rather straight-forward still
portable rule for the distribution of the relations across of the
slots like something I mentioned above (which is not the best thing
depending on the sizes and the number of tables), that would be quite
tricky IMO.
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message shveta malik 2022-12-19 11:27:29 Re: BUG #17716: walsender process hang while decoding 'DROP PUBLICATION' XLOG
Previous 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)

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2022-12-19 03:36:25 Re: [PATCH] random_normal function
Previous Message Michael Paquier 2022-12-19 03:16:18 Re: [BUG] pg_upgrade test fails from older versions.