Re: autovacuum process (PID ...) was terminated by signal 11

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Brian Hirt <bhirt(at)mobygames(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Subject: Re: autovacuum process (PID ...) was terminated by signal 11
Date: 2006-01-04 18:31:09
Message-ID: 4286.1136399469@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Brian Hirt <bhirt(at)mobygames(dot)com> writes:
> I can analyze that table without problems. I don't know if it's the
> same table every time. I'm trying to set up a development
> environment where i can test this stuff better without messing up our
> production systems. The table does have an expresional index.

I've managed to reproduce this: the triggering condition is that a
single autovac iteration has to VACUUM one table and then ANALYZE
(no vac) another table that has an expressional index with a plpgsql
function. It looks like we missed a path of control where
ActiveSnapshot has to be re-set-up, but I'm not clear where.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Brian Hirt 2006-01-04 18:37:39 Re: autovacuum process (PID ...) was terminated by signal 11
Previous Message Brian Hirt 2006-01-04 17:55:53 Re: autovacuum process (PID ...) was terminated by signal 11