Re: pg_upgrade bug found!
Bruce Momjian <bruce@momjian.us>
From: Bruce Momjian <bruce@momjian.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgresql.org
Date: 2011-04-08T21:58:00Z
Lists: pgsql-hackers
Tom Lane wrote: > Josh Berkus <josh@agliodbs.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@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +