Re: BUG #5669: server process was terminated by exception 0xC0000005
От | Alvaro Herrera |
---|---|
Тема | Re: BUG #5669: server process was terminated by exception 0xC0000005 |
Дата | |
Msg-id | 1285105776-sup-4246@alvh.no-ip.org обсуждение исходный текст |
Ответ на | Re: BUG #5669: server process was terminated by exception 0xC0000005 (Andrew Geery <andrew.geery@gmail.com>) |
Ответы |
Re: BUG #5669: server process was terminated by exception 0xC0000005
|
Список | pgsql-bugs |
Excerpts from Andrew Geery's message of mar sep 21 16:37:20 -0400 2010: > Running the server in debug mode, I see the following before the > server crashes -- it looks like something goes wrong with > autovac_balance_cost when trying to analyze the collection table (that > was the table the inserts were being done into). > > Thanks Hmm, can you get a stack trace? Please see http://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Windows Probably the easiest way to catch a dying autovacuum process is to set a very high value of vacuum_cost_delay, so that it sleeps for long enough that you can attach to it with the debugger before it dies. Thanks -- Ãlvaro Herrera <alvherre@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support
В списке pgsql-bugs по дате отправления: