Skip site navigation (1) Skip section navigation (2)

Re: BUG #5151: autovacuum process segfaults when max_fsm_pages are too low

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Boris Folgmann <boris(at)folgmann(dot)de>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5151: autovacuum process segfaults when max_fsm_pages are too low
Date: 2009-10-30 19:09:13
Message-ID: 4AEB39D9.4030403@enterprisedb.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Boris Folgmann wrote:
> Currently I'm using postgresql-8.1.15-1.el4s1.1 from the centosplus
> repository for CentOS 4.8. All updates applied, kernel is
> 2.6.9-89.0.11.ELsmp.
> I know that 8.1.18 is out, but haven't found something in the release-notes
> about problems with max_fsm_pages. Anyway, there isn't any more recent RPM
> available at the moment.

I don't think this is related to fsm, actually. Seems like something in
autovacuum, and there was this fix in 8.1.16 (from the release notes):

      Fix crash in autovacuum (Alvaro)

      The crash occurs only after vacuuming a whole database for
anti-transaction-wraparound purposes, which means that it occurs
infrequently and is hard to track down.

So I would suggest upgrading. If that doesn't help, and you can
reproduce the issue, a backtrace from a core dump would be nice.

-- 
  Heikki Linnakangas
  EnterpriseDB   http://www.enterprisedb.com

In response to

pgsql-bugs by date

Next:From: Tom LaneDate: 2009-10-30 21:14:13
Subject: Re: BUG #5153: Problem configuring postgresql-8.5alpha2 with SSL
Previous:From: Tom LaneDate: 2009-10-30 19:03:50
Subject: Re: BUG #5145: Complex query with lots of LEFT JOIN causes segfault

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group