Re: Upgrading a database dump/restore
| От | Tom Lane |
|---|---|
| Тема | Re: Upgrading a database dump/restore |
| Дата | |
| Msg-id | 13687.1160092587@sss.pgh.pa.us обсуждение |
| Ответ на | Upgrading a database dump/restore ("Mark Woodward" <pgsql@mohawksoft.com>) |
| Ответы |
Re: Upgrading a database dump/restore
Re: Upgrading a database dump/restore |
| Список | 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 по дате отправления: