Re: pg_upgrade bug found!

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Jeff Davis" <pgsql(at)j-davis(dot)com>, "Bruce Momjian" <bruce(at)momjian(dot)us>
Cc: "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(dot)com>, "Robert Haas" <robertmhaas(at)gmail(dot)com>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>, "RhodiumToad on IRC" <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
Subject: Re: pg_upgrade bug found!
Date: 2011-04-07 21:38:13
Message-ID: 4D9DE875020000250003C55D@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2011-04-07 21:47:00 Re: pg_upgrade bug found!
Previous Message Bruce Momjian 2011-04-07 21:36:10 Re: pg_upgrade bug found!