Re: Back end dies...
От | Arsalan Zaidi |
---|---|
Тема | Re: Back end dies... |
Дата | |
Msg-id | 016c01c1ccc7$2cb1e9e0$4301a8c0@directi.com обсуждение исходный текст |
Ответ на | Re: Back end dies... (Stephan Szabo <sszabo@megazone23.bigpanda.com>) |
Список | pgsql-general |
Could this be happening if I'm running out of Mem+Swap in the middle of a query? --Arsalan. > > > > Does your server log have any entries at around that point for the actual > > backend death? Do you have a core file? > > No core file, but here's the stuff from the log. Strange, I don't remember > kill -9'ing the backend... > > > DEBUG: server process (pid 26460) was terminated by signal 9 > DEBUG: terminating any other active server processes > NOTICE: Message from PostgreSQL backend: > The Postmaster has informed me that some other backend > died abnormally and possibly corrupted shared memory. > I have rolled back the current transaction and am > going to terminate your database system connection and exit. > Please reconnect to the database system and repeat your query. > DEBUG: all server processes terminated; reinitializing shared memory and > semaphores > DEBUG: database system was interrupted at 2002-03-15 20:56:17 IST > DEBUG: checkpoint record is at 33/CBC5968 > DEBUG: redo record is at 33/CBC5968; undo record is at 0/0; shutdown FALSE > DEBUG: next transaction id: 5946; next oid: 783000267 > DEBUG: database system was not properly shut down; automatic recovery in > progress > DEBUG: ReadRecord: record with zero length at 33/CBC59A8 > DEBUG: redo is not required > DEBUG: database system is ready > > > > > > ---------------------------(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 >
В списке pgsql-general по дате отправления: