Re: pg_upgrade bug found!

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_upgrade bug found!
Date: 2011-04-08 22:23:13
Message-ID: 201104082223.p38MND400651@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian wrote:
> 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?

Josh Berkus helped me get lots more details on a wiki page for this:

http://wiki.postgresql.org/wiki/20110408pg_upgrade_fix

I will reference the wiki in the email announcement.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2011-04-08 23:00:19 Re: pg_upgrade bug found!
Previous Message Robert Haas 2011-04-08 22:05:01 pgindent