Re: pg_dump new version
От | Wang, Mary Y |
---|---|
Тема | Re: pg_dump new version |
Дата | |
Msg-id | FA20D4C4FEBFD148B1C0CB09913825FC01EBDEF642@XCH-SW-06V.sw.nos.boeing.com обсуждение исходный текст |
Ответ на | Re: pg_dump new version (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-general |
I'm not clear when you said that "old pg_dump should work fine for this purpose in practically all cases, so it's not worthyour trouble to try to figure out a workaround". Did you mean that it's OK to use the old version of pg_dump when youare doing a major version upgrade when working with a RPM package? Thanks Mary -----Original Message----- From: pgsql-general-owner@postgresql.org [mailto:pgsql-general-owner@postgresql.org] On Behalf Of Tom Lane Sent: Tuesday, February 23, 2010 7:47 AM To: Oliver Kohll - Mailing Lists Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] pg_dump new version Oliver Kohll - Mailing Lists <oliver.lists@gtwm.co.uk> writes: > May I take a lull between PG releases to ask an upgrade Q? Documentation and people often recommend that when doing a majorversion upgrade, to dump data from the old server with the new version of pg_dump, since the new pg_dump may have bugfixesnot available to the old. > ... > So for someone using RPM packages to install Postgres, what's the recommended sequence to do this? There isn't any especially good way to do it with the RPM packages (at least not the ones from Red Hat or PGDG), becauseyou can't concurrently install different versions. In practice the old pg_dump should work fine for this purposein practically all cases, so it's not worth your trouble to try to figure out a workaround. (I am hoping that in 9.0 we have a better upgrade path for RPM installations.) regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
В списке pgsql-general по дате отправления: