| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pg_upgrade bug found! |
| Date: | 2011-04-08 21:58:00 |
| Message-ID: | 201104082158.p38Lw0619012@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Josh Berkus <josh(at)agliodbs(dot)com> writes:
> >> -- It will not lock any tables but will generate I/O.
>
> > add:
> > IMPORTANT: Depending on the size and configuration of your database,
> > this script may generate a lot of I/O and degrade database performance.
> > Users should execute this script during a low traffic period and watch
> > the database load.
>
> It might be worth suggesting that people can adjust their vacuum delay
> parameters to control the I/O load.
I talked to Tom about this and I am worried people will adjust it so it
takes days to complete. Is that a valid concern? Does anyone have a
suggested value?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-04-08 22:05:01 | pgindent |
| Previous Message | Kevin Grittner | 2011-04-08 21:54:51 | Re: getting to beta |