Re: Hardening pg_upgrade
| От | Kevin Grittner |
|---|---|
| Тема | Re: Hardening pg_upgrade |
| Дата | |
| Msg-id | 1408973652.16409.YahooMailNeo@web122303.mail.ne1.yahoo.com обсуждение исходный текст |
| Ответ на | Re: Hardening pg_upgrade (Bernd Helmle <mailings@oopsware.de>) |
| Ответы |
Re: Hardening pg_upgrade
|
| Список | pgsql-hackers |
Bernd Helmle <mailings@oopsware.de> wrote: > Magnus Hagander <magnus@hagander.net> wrote: >>> I vote for discarding 8.3 support in pg_upgrade. There are already >>> enough limitations on pg_upgrade from pre-8.4 to make it of questionable >>> value; if it's going to create problems like this, it's time to cut the >>> rope. >> >> +1. 8.3 has been unsupported for a fairly long time now, and you can >> still do a two-step upgrade if you're on that old a version. > > Also +1 from my side. I've seen some old 8.3 installations at customers, > still, but they aren't large and can easily be upgraded with a two step > upgrade. +1 If we could leave it without it being any extra work, fine; but once a release is over a year out of support, if it's a matter of putting extra work on the pg hackers or on the users who have chosen to wait more than a year after support ends to do the upgrade, I'm OK with asking those users to do a two-phase upgrade or fall back to pg_dump. It's not like we're leaving them without any options. -- Kevin Grittner EDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: