| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Euler Taveira <euler(at)timbira(dot)com(dot)br> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_upgrade vs vacuum_cost_delay |
| Date: | 2016-06-16 14:45:14 |
| Message-ID: | CABUevExrabwyBfQzOyM_SJujxrwPp69hHPORT3Tzo85uGEWFkw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jun 16, 2016 at 4:35 PM, Euler Taveira <euler(at)timbira(dot)com(dot)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.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2016-06-16 14:49:46 | Re: forcing a rebuild of the visibility map |
| Previous Message | Euler Taveira | 2016-06-16 14:35:56 | Re: pg_upgrade vs vacuum_cost_delay |