Thread: PgSQL Down

PgSQL Down

From
"Cavit Keskin"
Date:
Using Postgresql's source files I compiled postgresql 7.4.1 on a
dedicated machine with a customized Redhat 7.2 system.
Postgresql often stops after a time (unknown, changing).
Below is the log file just after Postgresql database server is started
manually. Log can't record the cause of this problem.

_____________________
LOG:  could not create IPv6 socket: Address family not supported by
protocol
LOG:  database system was interrupted at 2004-01-27 03:18:09 CST
LOG:  checkpoint record is at 0/4470A6C
LOG:  redo record is at 0/4470A6C; undo record is at 0/0; shutdown FALSE
LOG:  next transaction ID: 1275; next OID: 234555
LOG:  database system was not properly shut down; automatic recovery in
progress
LOG:  record with zero length at 0/4470AAC
LOG:  redo is not required
LOG:  database system is ready
______________________________________


Please note that I don't experience such a problem on a Slackware 9.0
system.


Cavit Keskin
cavit@binbir.net



Re: [SQL] PgSQL Down

From
Devrim GUNDUZ
Date:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Hi,

On Tue, 27 Jan 2004, Cavit Keskin wrote:

> Using Postgresql's source files I compiled postgresql 7.4.1 on a
> dedicated machine with a customized Redhat 7.2 system.
> Postgresql often stops after a time (unknown, changing).
> Below is the log file just after Postgresql database server is started
> manually. Log can't record the cause of this problem.
<snip> 

Could be something with hardware or power failure?

Also, could you please increase logging level (log_min_messages in 
postgresql.conf)?

Regards,
- -- 
Devrim GUNDUZ           
devrim@gunduz.org                devrim.gunduz@linux.org.tr         http://www.TDMSoft.com
http://www.gunduz.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFAFlGntl86P3SPfQ4RAsRMAKDnFnGylSZJc4rgmGv8FZWaVFhg1gCdE1n4
Z6BPzsEXBcYkJV1UIQPiiYY=
=uK9h
-----END PGP SIGNATURE-----



Re: PgSQL Down

From
Tom Lane
Date:
"Cavit Keskin" <cavit@binbir.net> writes:
> Postgresql often stops after a time (unknown, changing).

You haven't given any information that would allow anyone to help :-(

> Below is the log file just after Postgresql database server is started
> manually. Log can't record the cause of this problem.

We need to see the log entries from before the crash, not after.
        regards, tom lane