| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Robert Haas" <robertmhaas(at)gmail(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>, "Jeff Davis" <pgsql(at)j-davis(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 20:39:25 |
| Message-ID: | 4D9DDAAD020000250003C543@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> ISTM we need to force a minor release once we are sure this has
> been corrected. We had also probably put out an announcement
> warning people that have already used pg_upgrade of possible data
> corruption. I'm not sure exactly what the language around that
> should be, but this does seem pretty bad.
We just used this to upgrade all of our databases to 9.0. Most of
those (particularly the databases where data originates) have VACUUM
FREEZE ANALYZE run nightly, and we ran this against all databases
right after each pg_upgrade. Will that have offered us some
protection from this bug?
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | AAMIR KHAN | 2011-04-07 20:49:48 | Re: GSoC 2011 Eager MV implementation proposal |
| Previous Message | Kevin Grittner | 2011-04-07 20:34:19 | Re: SSI bug? |