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).
Hmm, can you get a stack trace? Please see
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.
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
In response to
pgsql-bugs by date
|Next:||From: Jeff Davis||Date: 2010-09-22 07:05:23|
|Subject: UNLISTEN bug|
|Previous:||From: Jairo Carrillo||Date: 2010-09-21 20:54:55|
|Subject: BUG #5671: ERROR: out of memory|