Tom Lane writes:
> FWIW, I would *never* trust a production database to pg_upgrade in its
> current state; it's untested and can't possibly get enough testing
> before release to be trustable. But if Bruce wants to work on it,
> where's the harm?
There isn't any harm working on it, but the question was whether we want
to enable it in the 7.2 release. Given that you would "never" trust it in
its current state, and me just having seen the actual code, I think that
it's barely worth being put into contrib. Where in fact it should
probably go.
> The only mistake we could make here is to advertise pg_upgrade as
> reliable. Which we will not do.
Or ship pg_upgrade in a default installation and undermine the reliability
reputation for people who don't read advertisements.
--
Peter Eisentraut peter_e@gmx.net