pg.ddx.io pgsql-sql@postgresql.org mailing list archive
help / color / mirror / Atom feedPgSQL Down
3+ messages / 3 participants
[nested] [flat]
* PgSQL Down
@ 2004-01-27 11:36 Cavit Keskin <cavit@binbir.net>
2004-01-27 11:55 ` Re: [SQL] PgSQL Down Devrim GUNDUZ <devrim@gunduz.org>
2004-01-27 16:58 ` Re: PgSQL Down Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 2 replies; 3+ messages in thread
From: Cavit Keskin @ 2004-01-27 11:36 UTC (permalink / raw)
To: pgsql-sql; +Cc: pgsql-bugs@postgresql.org
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
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: [SQL] PgSQL Down
2004-01-27 11:36 PgSQL Down Cavit Keskin <cavit@binbir.net>
@ 2004-01-27 11:55 ` Devrim GUNDUZ <devrim@gunduz.org>
1 sibling, 0 replies; 3+ messages in thread
From: Devrim GUNDUZ @ 2004-01-27 11:55 UTC (permalink / raw)
To: Cavit Keskin <cavit@binbir.net>; +Cc: pgsql-sql
-----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-----
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: PgSQL Down
2004-01-27 11:36 PgSQL Down Cavit Keskin <cavit@binbir.net>
@ 2004-01-27 16:58 ` Tom Lane <tgl@sss.pgh.pa.us>
1 sibling, 0 replies; 3+ messages in thread
From: Tom Lane @ 2004-01-27 16:58 UTC (permalink / raw)
To: Cavit Keskin <cavit@binbir.net>; +Cc: pgsql-sql; pgsql-bugs@postgresql.org
"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
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2004-01-27 16:58 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2004-01-27 11:36 PgSQL Down Cavit Keskin <cavit@binbir.net>
2004-01-27 11:55 ` Devrim GUNDUZ <devrim@gunduz.org>
2004-01-27 16:58 ` Tom Lane <tgl@sss.pgh.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox