| From: | Michael Banck <mbanck(at)gmx(dot)net> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(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 12:10:01 |
| Message-ID: | 6560929a.a70a0220.2576a.6c6e@mx.google.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)gmx(dot)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 | Content-Type | Size |
|---|---|---|
| 0001-Add-no-cost-delay-option-to-vacuumdb.patch | text/x-diff | 4.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zhijie Hou (Fujitsu) | 2023-11-24 12:21:46 | RE: pgoutput incorrectly replaces missing values with NULL since PostgreSQL 15 |
| Previous Message | Amit Kapila | 2023-11-24 11:47:05 | Re: pgoutput incorrectly replaces missing values with NULL since PostgreSQL 15 |