Re: pg_upgrade vs vacuum_cost_delay - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: pg_upgrade vs vacuum_cost_delay
Date
Msg-id CABUevExrabwyBfQzOyM_SJujxrwPp69hHPORT3Tzo85uGEWFkw@mail.gmail.com
Whole thread Raw
In response to Re: pg_upgrade vs vacuum_cost_delay  (Euler Taveira <euler@timbira.com.br>)
Responses Re: [HACKERS] pg_upgrade vs vacuum_cost_delay  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On Thu, Jun 16, 2016 at 4:35 PM, Euler Taveira <euler@timbira.com.br> wrote:
On 16-06-2016 09:05, Magnus Hagander wrote:
> Shouldn't pg_upgrade turn off vacuum cost delay when it vacuums the new
> cluster? Not talking about the post-analyze script, but when it runs
> vacuumdb to analyze and freeze before loading the new schema, in
> prepare_new_cluster()? Those run during downtime, so it seems like you'd
> want those to run as fast as possible.
>
Doesn't --new-options do the job?

You could, but it seems like it should do it by default. 


--

pgsql-hackers by date:

Previous
From: Euler Taveira
Date:
Subject: Re: pg_upgrade vs vacuum_cost_delay
Next
From: Kevin Grittner
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Avoid extra locks in GetSnapshotData if old_snapshot_threshold <