Re: help getting a backtrace from 9.2 on Ubuntu 13.04?
От | Jeff Janes |
---|---|
Тема | Re: help getting a backtrace from 9.2 on Ubuntu 13.04? |
Дата | |
Msg-id | CAMkU=1z9ZoaVv-fr=AJk9N1QfTtODg64e0AHWfE8RoTi5pCXXQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: help getting a backtrace from 9.2 on Ubuntu 13.04? (Chris Curvey <ccurvey@zuckergoldberg.com>) |
Ответы |
Re: help getting a backtrace from 9.2 on Ubuntu 13.04?
|
Список | pgsql-general |
Great thought. Looking through the logs, it appears that all my failures are on a CREATE INDEX. Usually on my biggest table, but often on another table.
2013-09-10 10:09:46 EDT ERROR: canceling autovacuum task
2013-09-10 10:09:46 EDT CONTEXT: automatic analyze of table "certified_mail_ccc2.public.cm_status_history"
2013-09-10 10:15:13 EDT LOG: server process (PID 14386) was terminated by signal 11: Segmentation fault
2013-09-10 10:15:13 EDT DETAIL: Failed process was running: CREATE INDEX cm_envelope_tracking_number ON cm_envelope USING btree (tracking_number);
2013-09-10 10:15:13 EDT LOG: terminating any other active server processes
2013-09-10 10:15:13 EDT WARNING: terminating connection because of crash of another server process
2013-09-10 10:15:13 EDT 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.
I cannot square this with the fact that when I echo the commands, the last echoed command is about setting privileges.
В списке pgsql-general по дате отправления: