Re: [HACKERS] pg_upgrade vs vacuum_cost_delay - Mailing list pgsql-hackers

From Michael Banck
Subject Re: [HACKERS] pg_upgrade vs vacuum_cost_delay
Date
Msg-id 6560929a.a70a0220.2576a.6c6e@mx.google.com
Whole thread Raw
In response to Re: [HACKERS] pg_upgrade vs vacuum_cost_delay  (Magnus Hagander <magnus@hagander.net>)
Responses Re: [HACKERS] pg_upgrade vs vacuum_cost_delay
List pgsql-hackers
Hi,

On Fri, Nov 24, 2023 at 12:17:56PM +0100, Magnus Hagander wrote:
> On Fri, Nov 24, 2023 at 11:21 AM Michael Banck <mbanck@gmx.net> wrote:
> > 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? :)

You're right, I somehow only saw your mail after I had already sent
mine.

To make up for this, I created a patch that implements our propoals, see
attached.


Michael

Attachment

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: pgoutput incorrectly replaces missing values with NULL since PostgreSQL 15
Next
From: "Zhijie Hou (Fujitsu)"
Date:
Subject: RE: pgoutput incorrectly replaces missing values with NULL since PostgreSQL 15