Re: pg_restore: error returned by PQputline - Mailing list pgsql-general
From | Clodoaldo Pinto Neto |
---|---|
Subject | Re: pg_restore: error returned by PQputline |
Date | |
Msg-id | 20040830014029.42006.qmail@web40905.mail.yahoo.com Whole thread Raw |
In response to | Re: pg_restore: error returned by PQputline (Tom Lane <tgl@sss.pgh.pa.us>) |
Responses |
Re: pg_restore: error returned by PQputline
|
List | pgsql-general |
--- Tom Lane <tgl@sss.pgh.pa.us> escreveu: > Look in the > postmaster's log to see what happened. > LOG: recycled transaction log file "0000002B0000007B" LOG: recycled transaction log file "0000002B0000007A" LOG: recycled transaction log file "0000002B00000079" LOG: checkpoints are occurring too frequently (17 seconds apart) HINT: Consider increasing the configuration parameter "checkpoint_segments". LOG: server process (PID 9576) was terminated by signal 9 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. CONTEXT: writing block 767665 of relation 463888/463894 LOG: all server processes terminated; reinitializing LOG: database system was interrupted at 2004-08-29 22:08:55 BRT LOG: checkpoint record is at 2B/81896F18 LOG: redo record is at 2B/7F6E7230; undo record is at 0/0; shutdown FALSE LOG: next transaction ID: 41275; next OID: 882451 LOG: database system was not properly shut down; automatic recovery in progress LOG: redo starts at 2B/7F6E7230 LOG: unexpected pageaddr 2B/76C1E000 in log file 43, segment 130, offset 12705792 LOG: redo done at 2B/82C1BD08 LOG: recycled transaction log file "0000002B0000007D" LOG: recycled transaction log file "0000002B0000007C" LOG: removing transaction log file "0000002B0000007E" LOG: database system is ready From postgresql.conf: #checkpoint_segments = 3 # in logfile segments, min 1, 16MB each /var/log/messages: Aug 29 22:31:31 s1 kernel: oom-killer: gfp_mask=0x1d2 Aug 29 22:31:33 s1 kernel: DMA per-cpu: Aug 29 22:31:33 s1 kernel: cpu 0 hot: low 2, high 6, batch 1 Aug 29 22:31:33 s1 kernel: cpu 0 cold: low 0, high 2, batch 1 Aug 29 22:31:33 s1 kernel: Normal per-cpu: Aug 29 22:31:33 s1 kernel: cpu 0 hot: low 32, high 96, batch 16 Aug 29 22:31:33 s1 kernel: cpu 0 cold: low 0, high 32, batch 16 Aug 29 22:31:33 s1 kernel: HighMem per-cpu: empty Aug 29 22:31:33 s1 kernel: Aug 29 22:31:33 s1 kernel: Free pages: 3408kB (0kB HighMem) Aug 29 22:31:33 s1 kernel: Active:100779 inactive:81540 dirty:0 writeback:0 unstable:0 free:852 slab:2537 mapped:174822 pagetables:1417 Aug 29 22:31:33 s1 kernel: DMA free:1744kB min:16kB low:32kB high:48kB active:5404kB inactive:5196kB present:16384kB Aug 29 22:31:33 s1 kernel: protections[]: 8 436 436 Aug 29 22:31:33 s1 kernel: Normal free:1664kB min:856kB low:1712kB high:2568kB active:397712kB inactive:320964kB present:753600kB Aug 29 22:31:33 s1 kernel: protections[]: 0 428 428 Aug 29 22:31:34 s1 kernel: HighMem free:0kB min:128kB low:256kB high:384kB active:0kB inactive:0kB present:0kB Aug 29 22:31:34 s1 kernel: protections[]: 0 0 0 Aug 29 22:31:35 s1 kernel: DMA: 4*4kB 8*8kB 14*16kB 1*32kB 0*64kB 1*128kB 1*256kB 2*512kB 0*1024kB 0*2048kB 0*4096kB = 1744kB Aug 29 22:31:35 s1 kernel: Normal: 0*4kB 0*8kB 0*16kB 0*32kB 0*64kB 1*128kB 0*256kB 1*512kB 1*1024kB 0*2048kB 0*4096kB = 1664kB Aug 29 22:31:36 s1 kernel: HighMem: empty Aug 29 22:31:36 s1 kernel: Swap cache: add 1273826, delete 1273816, find 26834/46799, race 0+109 Aug 29 22:31:36 s1 kernel: Out of Memory: Killed process 9576 (postmaster). Regards, Clodoaldo Pinto _______________________________________________________ Yahoo! Acesso Grátis - navegue de graça com conexão de qualidade! http://br.acesso.yahoo.com/
pgsql-general by date: