[pgsql-jp: 40466] "PANIC: right sibling's left-link doesn't match"ログ出力に対する対処方法について

bobby midtown0128 @ mail.bbexcite.jp
2010年 10月 21日 (木) 12:15:02 JST


湯沢と言います。

postgres8.1.8をWindowsで使用しています。

postgresのログに以下の出力がされた場合の対処方法を教えていただければ幸いで
す。

以下の繰りしを行っています。
1.INSERT の実行
2.PANIC エラー出力
3.terminate application
4.database system was not properly shut down; automatic recovery in
progress
5.database system is starting up

この「PANIC」を回避したいと考えていますがどの様に対処したらよいでしょうか。

よろしくお願いいたします。


***エラーログの一部***
STATEMENT:  INSERT INTO atble_a(abc,def....) VALUES (data1,data2...)
PANIC:  right sibling's left-link doesn't match
STATEMENT:  INSERT INTO atble_a(abc,def....) VALUES (data1,data2...)

This application has requested the Runtime to terminate it in an unusual
way.
Please contact the application's support team for more information.
LOG:  server process (PID 4220) was terminated by signal 3
LOG:  terminating any other active server processes
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.
FATAL:  the database system is in recovery mode
 ・
 ・
 ・
 ・
LOG:  all server processes terminated; reinitializing
LOG:  database system was interrupted at 2010-10-20 06:12:52 東京 (標準時)
LOG:  checkpoint record is at CBE/5F804B18
LOG:  redo record is at CBE/5F804B18; undo record is at 0/0; shutdown TRUE
LOG:  next transaction ID: 210989648; next OID: 126296
LOG:  next MultiXactId: 1; next MultiXactOffset: 0
LOG:  database system was not properly shut down; automatic recovery in
progress
LOG:  redo starts at CBE/5F804B60
FATAL:  the database system is starting up
LOG:  unexpected pageaddr CBD/F84C4000 in log file 3262, segment 123, offset
4997120
LOG:  redo done at CBE/7B4C3F68
FATAL:  the database system is starting up
LOG:  database system is ready
LOG:  transaction ID wrap limit is 2147484146, limited by database
"postgres"
 ・
 ・
 ・
 ・
TopMemoryContext: 49152 total in 5 blocks; 11704 free (12 chunks); 37448
used
TopTransactionContext: 8192 total in 1 blocks; 7856 free (0 chunks); 336
used
Record information cache: 8192 total in 1 blocks; 1864 free (0 chunks); 6328
used
Operator class cache: 8192 total in 1 blocks; 4936 free (0 chunks); 3256
used
MessageContext: 24576 total in 2 blocks; 4368 free (3 chunks); 20208 used
CFuncHash: 8192 total in 1 blocks; 4936 free (0 chunks); 3256 used
smgr relation table: 8192 total in 1 blocks; 2872 free (0 chunks); 5320 used
Portal hash: 8192 total in 1 blocks; 3912 free (0 chunks); 4280 used
PortalMemory: 8192 total in 1 blocks; 8040 free (0 chunks); 152 used
PortalHeapMemory: 1024 total in 1 blocks; 864 free (0 chunks); 160 used
ExecutorState: 904912896 total in 131 blocks; 3480 free (110 chunks);
904909416 used
ExprContext: 8192 total in 1 blocks; 8176 free (1 chunks); 16 used
ExprContext: 8192 total in 1 blocks; 8160 free (1 chunks); 32 used
Relcache by OID: 8192 total in 1 blocks; 3376 free (0 chunks); 4816 used
CacheMemoryContext: 516096 total in 6 blocks; 152936 free (1 chunks); 363160
used
 ・
 ・
 ・
MdSmgr: 8192 total in 1 blocks; 7240 free (0 chunks); 952 used
LockTable (locallock hash): 8192 total in 1 blocks; 3912 free (0 chunks);
4280 used
Timezones: 48408 total in 2 blocks; 5968 free (0 chunks); 42440 used
ErrorContext: 8192 total in 1 blocks; 8176 free (0 chunks); 16 used
ERROR:  out of memory
DETAIL:  Failed on request of size 20.

STATEMENT:  INSERT INTO atble_a(abc,def....) VALUES (data1,data2...)
PANIC:  right sibling's left-link doesn't match
STATEMENT:  INSERT INTO atble_a(abc,def....) VALUES (data1,data2...)





pgsql-jp メーリングリストの案内