Re: [HACKERS] pg_upgrade vs vacuum_cost_delay

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Michael Banck <mbanck(at)gmx(dot)net>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Euler Taveira <euler(at)timbira(dot)com(dot)br>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] pg_upgrade vs vacuum_cost_delay
Date: 2023-11-24 11:17:56
Message-ID: CABUevEx1MXLGwZZheHe1gf3edYrupmS0N+4w1B_VU+c8qtNSWQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Nov 24, 2023 at 11:21 AM Michael Banck <mbanck(at)gmx(dot)net> wrote:
>
> Hi,
>
> On Wed, Nov 22, 2023 at 11:23:34PM -0500, Bruce Momjian wrote:
> > + Non-zero values of
> > + <varname>vacuum_cost_delay</varname> will delay statistics generation.
>
> Now I wonder wheter vacuumdb maybe should have an option to explicitly
> force vacuum_cost_delay to 0 (I don't think it has?)?

That's exactly what I proposed, isn't it? :)

--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Shlok Kyal 2023-11-24 11:35:00 Re: undetected deadlock in ALTER SUBSCRIPTION ... REFRESH PUBLICATION
Previous Message Ashutosh Bapat 2023-11-24 11:07:58 Re: Adding facility for injection points (or probe points?) for more advanced tests