Horton

Re: pg_upgrade bug found!

Kevin Grittner <kevin.grittner@wicourts.gov>

View thread
From: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
To: "Jeff Davis" <pgsql@j-davis.com>, "Bruce Momjian" <bruce@momjian.us>
Cc: "Alvaro Herrera" <alvherre@commandprompt.com>, "Heikki Linnakangas" <heikki.linnakangas@enterprisedb.com>, "Robert Haas" <robertmhaas@gmail.com>, "PostgreSQL-development" <pgsql-hackers@postgresql.org>, "RhodiumToad on IRC" <andrew@tao11.riddles.org.uk>
Date: 2011-04-07T21:38:13Z
Lists: pgsql-hackers 
Bruce Momjian <bruce@momjian.us> wrote:
 
> all we need to do is set those hint bits before the clog gets
> remove, so maybe just a SELECT * would do the trick!
 
Does that mean that those experiencing the problem are failing to do
the vacuumdb run which is recommended in the pg_upgrade instructions?
 
-Kevin