Greg Stark escribió:
> On Thu, May 9, 2013 at 10:11 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > In any case, it seems like pg_upgrade ought to have a strategy for
> > dealing with tables acquiring toast tables like this,
>
> Acquiring toast tables seems pretty trivial to deal with. *Losing* a
> toast table might be a bit more involved...
pg_upgrade already deals with the new code deciding not to create a
toast table (by forcing it to do so anyway in binary upgrade mode).
It's only the other case that's problematic -- but then AFAICS fixing
that is just a SMOP.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services