error explanation

Поиск
Список
Период
Сортировка
От Omachonu Ogali
Тема error explanation
Дата
Msg-id 20050519083149.GE5106@dipole.informationwave.net
обсуждение исходный текст
Ответы Re: error explanation  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-general
I deleted all the rows, approximately 3 million, in a table earlier in
the day, so during the nightly routine vacuum, I received the following:

dbname=# vacuum verbose analyze table;
INFO:  vacuuming "public.table"
INFO:  index "table_attempt_idx" now contains 3895682 row versions in 103829 pages
DETAIL:  0 index row versions were removed.
766 index pages have been deleted, 766 are currently reusable.
CPU 8.97s/1.13u sec elapsed 592.94 sec.
INFO:  index "table_search_idx" now contains 3383634 row versions in 19422 pages
DETAIL:  0 index row versions were removed.
3105 index pages have been deleted, 3105 are currently reusable.
CPU 0.61s/1.05u sec elapsed 33.01 sec.
INFO:  "table": removed 1397790 row versions in 34649 pages
DETAIL:  CPU 2.44s/1.60u sec elapsed 32.39 sec.
INFO:  index "table_attempt_idx" now contains 3147492 row versions in 103830 pages
DETAIL:  748304 index row versions were removed.
2906 index pages have been deleted, 766 are currently reusable.
CPU 12.00s/6.42u sec elapsed 599.79 sec.
INFO:  index "table_search_idx" now contains 2723871 row versions in 19422 pages
DETAIL:  659880 index row versions were removed.
6138 index pages have been deleted, 3102 are currently reusable.
CPU 0.85s/1.86u sec elapsed 33.22 sec.
INFO:  "table": removed 1397782 row versions in 34513 pages
DETAIL:  CPU 2.67s/1.30u sec elapsed 31.22 sec.
INFO:  index "table_attempt_idx" now contains 2405128 row versions in 103830 pages
DETAIL:  742508 index row versions were removed.
5721 index pages have been deleted, 765 are currently reusable.
CPU 11.65s/6.36u sec elapsed 603.68 sec.
INFO:  index "table_search_idx" now contains 2089828 row versions in 19422 pages
DETAIL:  634181 index row versions were removed.
9067 index pages have been deleted, 3101 are currently reusable.
CPU 0.79s/1.68u sec elapsed 34.13 sec.
INFO:  "table": removed 1397765 row versions in 34588 pages
DETAIL:  CPU 2.49s/1.47u sec elapsed 31.33 sec.
INFO:  index "table_attempt_idx" now contains 1690401 row versions in 103830 pages
DETAIL:  714856 index row versions were removed.
9965 index pages have been deleted, 764 are currently reusable.
CPU 11.54s/6.26u sec elapsed 590.81 sec.
INFO:  index "table_search_idx" now contains 1474467 row versions in 19422 pages
DETAIL:  615463 index row versions were removed.
11971 index pages have been deleted, 3101 are currently reusable.
CPU 0.87s/1.60u sec elapsed 49.51 sec.
INFO:  "table": removed 1397795 row versions in 34603 pages
DETAIL:  CPU 2.39s/1.23u sec elapsed 23.45 sec.
INFO:  index "table_attempt_idx" now contains 954707 row versions in 103830 pages
DETAIL:  735785 index row versions were removed.
19001 index pages have been deleted, 764 are currently reusable.
CPU 12.05s/6.34u sec elapsed 602.31 sec.
INFO:  index "table_search_idx" now contains 836578 row versions in 19422 pages
DETAIL:  637964 index row versions were removed.
14946 index pages have been deleted, 3101 are currently reusable.
CPU 0.76s/1.38u sec elapsed 34.35 sec.
INFO:  "table": removed 1397798 row versions in 34600 pages
DETAIL:  CPU 2.72s/1.46u sec elapsed 80.80 sec.
PANIC:  right sibling is not next child
server closed the connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.
The connection to the server was lost. Attempting reset: Failed.
!>

My logs displayed the following:
May 19 04:09:28 db1 /kernel: pid 66449 (postgres), uid 70: exited on signal 6 (core dumped)
May 19 04:09:28 db1 postgres[81721]: [5-1] LOG:  server process (PID 66449) was terminated by signal 6
May 19 04:09:28 db1 postgres[81721]: [6-1] LOG:  terminating any other active server processes
May 19 04:09:28 db1 postgres[77806]: [5-1] WARNING:  terminating connection because of crash of another server process
May 19 04:09:28 db1 postgres[77806]: [5-2] DETAIL:  The postmaster has commanded this server process to roll back the
currenttransaction and exit, because another server 
May 19 04:09:28 db1 postgres[77806]: [5-3]  process exited abnormally and possibly corrupted shared memory.
May 19 04:09:28 db1 postgres[77806]: [5-4] HINT:  In a moment you should be able to reconnect to the database and
repeatyour command. 
May 19 04:09:28 db1 postgres[78345]: [7-1] FATAL:  the database system is in recovery mode
May 19 04:09:28 db1 postgres[81721]: [7-1] LOG:  all server processes terminated; reinitializing
May 19 04:09:28 db1 postgres[78346]: [8-1] LOG:  database system was interrupted at 2005-05-19 04:09:22 EDT
May 19 04:09:28 db1 postgres[78346]: [9-1] LOG:  checkpoint record is at 16C/247F5468
May 19 04:09:28 db1 postgres[78346]: [10-1] LOG:  redo record is at 16C/1FA441B4; undo record is at 0/0; shutdown FALSE
May 19 04:09:28 db1 postgres[78346]: [11-1] LOG:  next transaction ID: 410726590; next OID: 143676535
May 19 04:09:28 db1 postgres[78346]: [12-1] LOG:  database system was not properly shut down; automatic recovery in
progress
May 19 04:09:28 db1 postgres[78346]: [13-1] LOG:  redo starts at 16C/1FA441B4
May 19 04:10:47 db1 postgres[78346]: [14-1] LOG:  record with zero length at 16C/35789CEC
May 19 04:10:47 db1 postgres[78346]: [15-1] LOG:  redo done at 16C/35789CC8
May 19 04:12:13 db1 postgres[78346]: [16-1] LOG:  recycled transaction log file "0000016C00000019"
May 19 04:12:13 db1 postgres[78346]: [17-1] LOG:  recycled transaction log file "0000016C0000001A"
May 19 04:12:13 db1 postgres[78346]: [18-1] LOG:  recycled transaction log file "0000016C0000001B"
May 19 04:12:13 db1 postgres[78346]: [19-1] LOG:  recycled transaction log file "0000016C0000001C"
May 19 04:12:13 db1 postgres[78346]: [20-1] LOG:  recycled transaction log file "0000016C0000001D"
May 19 04:12:13 db1 postgres[78346]: [21-1] LOG:  recycled transaction log file "0000016C0000001E"
May 19 04:12:13 db1 postgres[78346]: [22-1] LOG:  recycled transaction log file "0000016C00000000"
May 19 04:12:13 db1 postgres[78346]: [23-1] LOG:  recycled transaction log file "0000016C00000001"
May 19 04:12:13 db1 postgres[78346]: [24-1] LOG:  recycled transaction log file "0000016C00000002"
May 19 04:12:13 db1 postgres[78346]: [25-1] LOG:  recycled transaction log file "0000016C00000003"
May 19 04:12:13 db1 postgres[78346]: [26-1] LOG:  recycled transaction log file "0000016C00000004"
May 19 04:12:13 db1 postgres[78346]: [27-1] LOG:  recycled transaction log file "0000016C00000005"
May 19 04:12:13 db1 postgres[78346]: [28-1] LOG:  recycled transaction log file "0000016C00000006"
May 19 04:12:13 db1 postgres[78346]: [29-1] LOG:  recycled transaction log file "0000016C00000007"
May 19 04:12:13 db1 postgres[78346]: [30-1] LOG:  recycled transaction log file "0000016C00000008"
May 19 04:12:13 db1 postgres[78346]: [31-1] LOG:  recycled transaction log file "0000016C00000009"
May 19 04:12:13 db1 postgres[78346]: [32-1] LOG:  recycled transaction log file "0000016C0000000A"
May 19 04:12:13 db1 postgres[78346]: [33-1] LOG:  recycled transaction log file "0000016C0000000B"
May 19 04:12:13 db1 postgres[78346]: [34-1] LOG:  recycled transaction log file "0000016C0000000C"
May 19 04:12:13 db1 postgres[78346]: [35-1] LOG:  recycled transaction log file "0000016C0000000D"
May 19 04:12:13 db1 postgres[78346]: [36-1] LOG:  recycled transaction log file "0000016C0000000E"
May 19 04:12:13 db1 postgres[78346]: [37-1] LOG:  recycled transaction log file "0000016C0000000F"
May 19 04:12:13 db1 postgres[78346]: [38-1] LOG:  recycled transaction log file "0000016C00000010"
May 19 04:12:13 db1 postgres[78346]: [39-1] LOG:  recycled transaction log file "0000016C00000011"
May 19 04:12:13 db1 postgres[78346]: [40-1] LOG:  recycled transaction log file "0000016C00000012"
May 19 04:12:13 db1 postgres[78346]: [41-1] LOG:  recycled transaction log file "0000016C00000013"
May 19 04:12:13 db1 postgres[78346]: [42-1] LOG:  recycled transaction log file "0000016C00000014"
May 19 04:12:13 db1 postgres[78346]: [43-1] LOG:  recycled transaction log file "0000016C00000015"
May 19 04:12:13 db1 postgres[78346]: [44-1] LOG:  recycled transaction log file "0000016C00000016"
May 19 04:12:13 db1 postgres[78346]: [45-1] LOG:  recycled transaction log file "0000016C00000017"
May 19 04:12:13 db1 postgres[78346]: [46-1] LOG:  recycled transaction log file "0000016C00000018"
May 19 04:12:13 db1 postgres[78346]: [47-1] LOG:  database system is ready

Any thoughts?

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

Предыдущее
От: "Dinesh Pandey"
Дата:
Сообщение: How can I write trigger on a columns insert/update?
Следующее
От: Richard Huxton
Дата:
Сообщение: Re: How can I write trigger on a columns insert/update?