Robert Haas <robertmh...@gmail.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
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
