On Tue, Apr 30, 2013 at 12:02:59PM -0400, Robert Haas wrote:
> On Tue, Apr 30, 2013 at 10:40 AM, Kevin Grittner <kgrittn@ymail.com> wrote:
> >>> What is a real problem or risk with using this mechanism until we
> >>> engineer something better? What problems with converting to a
> >>> later major release does anyone see?
> >>
> >> Well, it's a pg_upgrade hazard, if nothing else, isn't it?
> >
> > I don't think so. What do you see as a problem?
>
> pg_upgrade only handles changes in catalog state, not on-disk
> representation. If the on-disk representation of an non-scannable
> view might change in a future release, it's a pg_upgrade hazard.
Yes, pg_upgrade is never going to write to data pages as that would be
slow and prevent the ability to roll back to the previous cluster on
error.
-- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB
http://enterprisedb.com
+ It's impossible for everything to be true. +
