Re: postgres dies while doing vacuum analyze
От | mordicus |
---|---|
Тема | Re: postgres dies while doing vacuum analyze |
Дата | |
Msg-id | 9gdn9b$g4c$1@news.tht.net обсуждение исходный текст |
Ответ на | postgres dies while doing vacuum analyze (Manuel Sugawara <masm@fciencias.unam.mx>) |
Список | pgsql-hackers |
Manuel Sugawara wrote: > Guys, > > Just installed a new data base in my server and while running vacuum > analyze postgres dies with the following message: > > [...] > NOTICE: Index pg_rewrite_oid_index: Pages 2; Tuples 16. CPU 0.00s/0.00u > sec. > NOTICE: Index pg_rewrite_rulename_index: Pages 2; Tuples 16. CPU > 0.00s/0.00u sec. > NOTICE: --Relation pg_toast_17058-- > NOTICE: Pages 4: Changed 0, reaped 0, Empty 0, New 0; Tup 17: Vac 0, > Keep/VTL 0/0, Crash 0, UnUsed 0, MinLen 219, MaxLen 2034; Re-using: > Free/Avail. Space 0/0; EndEmpty/Avail. Pages 0/0. CPU 0.00s/0.00u sec. > NOTICE: Index pg_toast_17058_idx: Pages 2; Tuples 17. CPU 0.00s/0.00u > sec. > NOTICE: Analyzing... > pqReadData() -- backend closed the channel unexpectedly. > This probably means the backend terminated abnormally > before or while processing the request. > The connection to the server was lost. Attempting reset: Failed. > !# > > The postgres version is 7.1.2 and the data base was initialized with > > $ LANG=es_MX /usr/bin/initdb -D /var/lib/pgsql/data -E latin1 > > It is running on Redhat Linux 7.1 i686 with 2.4.2-2 kernel. > Here is the back trace from gdb Try 2.4.5 Kernel, I have the same problem with Suse 7.1 2.4.2 Kernel, since update, no more problems
В списке pgsql-hackers по дате отправления: