Wierd panic with 7.4.7

Поиск
Список
Период
Сортировка
От Joshua D. Drake
Тема Wierd panic with 7.4.7
Дата
Msg-id 42C06782.5040401@commandprompt.com
обсуждение исходный текст
Ответы Re: Wierd panic with 7.4.7  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Hello,

Any thoughts on the below? Specifically the PANIC? A customer
was performing a full vacuum when it happen. This is running 7.4.7
on ES 3.0. We run daily vacuums and analyzes as well.

2005-06-27 16:35:02 LOG:  recycled transaction log file "0000004D0000006F"
2005-06-27 16:35:02 LOG:  recycled transaction log file "0000004D00000070"
2005-06-27 16:35:02 LOG:  recycled transaction log file "0000004D00000071"
2005-06-27 16:35:02 LOG:  recycled transaction log file "0000004D00000072"
2005-06-27 16:35:02 LOG:  recycled transaction log file "0000004D00000073"
2005-06-27 16:35:02 LOG:  recycled transaction log file "0000004D00000074"
2005-06-27 16:35:02 LOG:  recycled transaction log file "0000004D00000075"
2005-06-27 16:35:02 LOG:  recycled transaction log file "0000004D00000076"
2005-06-27 16:36:23 LOG:  incomplete startup packet
2005-06-27 16:37:53 ERROR:  could not send data to client: Broken pipe
2005-06-27 16:37:53 PANIC:  cannot abort transaction 146017848, it was 
already committed
2005-06-27 16:37:53 LOG:  server process (PID 6931) was terminated by 
signal 6
2005-06-27 16:37:53 LOG:  terminating any other active server processes
2005-06-27 16:37:53 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.
2005-06-27 16:37:53 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.

Sincerely,

Joshua D. Drake



-- 
Your PostgreSQL solutions company - Command Prompt, Inc. 1.800.492.2240
PostgreSQL Replication, Consulting, Custom Programming, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Michael Glaesemann
Дата:
Сообщение: GCC pointer signedness (and other) warnings
Следующее
От: Andreas Pflug
Дата:
Сообщение: Re: For review: Server instrumentation patch