Thread: restart postgres 7.3.2 problem

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

Saranya Sivakumar <sarlavk@yahoo.com> 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
(YourSystem'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

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@sss.pgh.pa.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

On 8/15/05 11:19 AM, "Saranya Sivakumar" <sarlavk@yahoo.com> wrote:

> 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?

My guess is that you need to start the server with tcp/ip connection enabled
(using the '-i' switch), but I may be wrong.

Hi,

I've skimmed the documentation and Googled for it, but
all I can find is *why* to do it and *what* it does,
not *how* a total novice should set up her machine to
vacuum once in a while :-)

I need a tutorial, or a set of instructions, for a XP
machine running pgSQL 8.0.3.

Thanks!



____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs

Saranya Sivakumar <sarlavk@yahoo.com> writes:
> 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

You seem to be rather seriously confused --- that is certainly not a 7.3
postmaster, because there was no IPv6 support in PG 7.3; nor was there a
writer subprocess before 8.0, so I'm betting this is actually 8.0.something.

It would appear that you've got two different generations of Postgres
installed on that machine, and they are fighting over which one owns the
database directory.  In fact, you may have pieces of *three* versions,
because it says here that RHL 7.3 shipped with Postgres 7.2.something.
This is a recipe for shooting yourself in the foot :-(.  I'd suggest
figuring out which version you actually wish to be running, and removing
all traces of the other version(s), and then making sure that the system
boot process correctly starts the version you want to run.

> 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.

8.0 defaults to accepting only local TCP connections; if you want it to
accept remote connections, set listen_addresses to '*' in
postgresql.conf (and restart the postmaster).  Pre-8.0, set tcpip_socket
to true, instead.

            regards, tom lane