Re: restart postgres 7.3.2 problem

Hi Tom,

Thanks for your input. Meanwhile, we tried starting postgres using this command and were successful according to the log:

su postgres -c "/usr/bin/pg_ctl start -D /db/data"

pg_ctl: another postmaster may be running; trying to start postmaster anyway

LOG: could not create IPv6 socket: Address family not supported by protocol

LOG: database system was interrupted at 2005-06-07 09:57:41 EDT

LOG: checkpoint record is at 3/1E712C0

LOG: redo record is at 3/1E712C0; undo record is at 0/0; shutdown FALSE

LOG: next transaction ID: 45903; next OID: 32170717

LOG: database system was not properly shut down; automatic recovery in progress

LOG: record with zero length at 3/1E712FC

LOG: redo is not required

LOG: database system is ready

postmaster starting

postgres 6791 0.1 0.2 15104 2704 pts/2 S 09:38 0:00 /usr/local/pgsql/bin/postmaster -D /db/data

postgres 6794 0.0 0.2 15104 2748 pts/2 S 09:38 0:00 postgres: writer process

postgres 6795 0.0 0.1 5988 1708 pts/2 S 09:38 0:00 postgres: stats buffer process

postgres 6796 0.0 0.1 4984 1808 pts/2 S 09:38 0:00 postgres: stats collector process

Though the log messages say that posgtres has started and is running, when we try to access the database from the web, we get an error message saying that Postgres is not running and accepting connections on port 5432.

Is there something we are missing out on?

Thanks,

Saranya

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
Saranya Sivakumar writes:
> We got the following message:

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

> Does this mean that we have to upgrade Postgres to a newer version?

This means that /var/lib/pgsql/data/PG_VERSION did not contain what the
init script expected to find (namely "7.3"). You need to figure out why
that happened --- and I'm afraid none of the likely explanations are
pleasant. The two that come to mind are (a) you've suffered disk
corruption or (b) somebody mistakenly overwrote the existing database
by initdb'ing with a different PG major version. Hope you've got a
recent backup...

regards, tom lane

---------------------------------
Start your day with Yahoo! - make it your home page