On May 24, 2004, at 9:19 PM, Mike G wrote:
Is it crashing around the time a pg_dump is executed? There is a similar problem with 7.4.1 on cygwin / windows.
There were some patches for this applied to 7.4.2 if that is the case.
On Mon, May 24, 2004 at 04:25:30PM -0500, Joe Lester wrote:I'm getting this message on Postgres 7.4.1 (Mac OS 10.3)
2004-05-24 15:20:15 WARNING: terminating connection because of crash
of another server process
DETAIL: The postmaster has commanded this server process to roll back
the current transaction and exit, because another server process exited
abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and
repeat your command.
This message repeats itself for each back-end that shuts down.
This is the second time in two days I've got this message in my log. The server has been running fine for about 5 months straight up until now. The load on the server has increased somewhat in the last few days, not in the number of back-end processes, but in the number of SELECTs each back-end performs.
Can someone give me any pointers on what troubleshooting steps I can take to get my system stable again?
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly
---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
