Re: Upgrading a database dump/restore - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Upgrading a database dump/restore
Date
Msg-id 13687.1160092587@sss.pgh.pa.us
Whole thread Raw
In response to Upgrading a database dump/restore  ("Mark Woodward" <pgsql@mohawksoft.com>)
Responses Re: Upgrading a database dump/restore  ("Guido Barosio" <gbarosio@gmail.com>)
Re: Upgrading a database dump/restore  ("Mark Woodward" <pgsql@mohawksoft.com>)
List pgsql-hackers
"Mark Woodward" <pgsql@mohawksoft.com> writes:
> Not to cause any arguments, but this is sort a standard discussion that
> gets brought up periodically and I was wondering if there has been any
> "softening" of the attitudes against an "in place" upgrade, or movement to
> not having to dump and restore for upgrades.

Whenever someone actually writes a pg_upgrade, we'll institute a policy
to restrict changes it can't handle.  But until we have a credible
upgrade tool it's pointless to make any such restriction.  ("Credible"
means "able to handle system catalog restructurings", IMHO --- without
that, you'd not have any improvement over the current rules for minor
releases.)
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_dump exclusion switches and functions/types
Next
From: Tom Lane
Date:
Subject: Re: continuing daily testing of dbt2 against postgresql