Обсуждение: upgrade issue

Поиск
Список
Период
Сортировка

upgrade issue

От
Jodi Kanter
Дата:
Our system admin recently upgraded our Linux system from 7.1 to 7.3.
Apparently this upgrade also changed our postgres version from 7.1.3 to
7.2.1-5.

We are now getting the following error:

> An old version of the database format was found.
> You need to upgrade the data format before using PostgreSQL.
> See (Your System's documentation directory)/postgresql-7.2/README.rpm-dist
> for more information.

I have now read (all be it to late) the documentation warning of this
problem. Luckily we do not have any data that I need to save in the
database. I could easily get back to a functioning state if I could drop the
database and rebuild it via my schema.sql file. However, I cannot drop the
database unless I can get the postmaster started.
Can anyone advise?

Also, the upgrade doc that I am reading makes mention of a postgres-dump
command but there is no documentation on the system referencing this
command. Can someone please tell me more about it? Is it a new command?

Thanks so much for your assistance.
Jodi


Re: upgrade issue

От
Tom Lane
Дата:
Jodi Kanter <jkanter@virginia.edu> writes:
> I have now read (all be it to late) the documentation warning of this
> problem. Luckily we do not have any data that I need to save in the
> database. I could easily get back to a functioning state if I could drop the
> database and rebuild it via my schema.sql file. However, I cannot drop the
> database unless I can get the postmaster started.

If you don't need any of the data then you can just rm -rf $PGDATA and
initdb.  (You might at least want to save the text configuration files
that appear in the top level $PGDATA directory, however, as consulting
them will make it easier to configure your new installation.)

            regards, tom lane

Re: upgrade issue

От
Dmitry Morozovsky
Дата:
On Fri, 16 Aug 2002, Jodi Kanter wrote:

JK> Our system admin recently upgraded our Linux system from 7.1 to 7.3.
JK> Apparently this upgrade also changed our postgres version from 7.1.3 to
JK> 7.2.1-5.

[snip]

JK> problem. Luckily we do not have any data that I need to save in the
JK> database. I could easily get back to a functioning state if I could drop the
JK> database and rebuild it via my schema.sql file. However, I cannot drop the
JK> database unless I can get the postmaster started.
JK> Can anyone advise?

Well if you do not neet older database then just 'rm -rf $PGDATA' and then
do initdb. You'll got virgin empty database cluster.

Sincerely,
D.Marck                                   [DM5020, DM268-RIPE, DM3-RIPN]
------------------------------------------------------------------------
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru ***
------------------------------------------------------------------------