Re: The lightbulb just went on... - Mailing list pgsql-hackers

From Tom Lane
Subject Re: The lightbulb just went on...
Date
Msg-id 1347.971799563@sss.pgh.pa.us
Whole thread Raw
In response to Re: The lightbulb just went on...  (Michael J Schout <mschout@gkg.net>)
Responses Re: The lightbulb just went on...  (Michael J Schout <mschout@gkg.net>)
List pgsql-hackers
Michael J Schout <mschout@gkg.net> writes:
> I think I may have been seeing this problem as well.  We were getting
> crashes very often with 7.0.2 during VACUUM's if activity was going
> on to our database during the vacuum (even though the activity was 
> light).  Our solution in the meantime was to simply disable the
> aplications during a vacuum to avoid any activity during hte vacuum,
> and we have not had a crash on vacuum since that happened.  If this
> sounds consistent with the problem you think Alfred is having,

Yes, it sure does.

The patch I have applies atop a previous change in the REL7_0_PATCHES
branch, so what I would recommend is that you pull the current state of
the REL7_0_PATCHES branch from our CVS server, and then you can test
what will shortly become 7.0.3.  There are several other critical bug
fixes in there since 7.0.2.

Dunno if you know how to use cvs, but the critical steps are explained
at http://www.postgresql.org/docs/postgres/x28786.htm.  Note that the
given recipe will pull current development tip, which is NOT what you
want.  In step 3, instead of doing... co -P pgsql
do... co -P -r REL7_0_PATCHES pgsql

Then configure and build as usual.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: bug: alter table/FK
Next
From: Jeff Hoffmann
Date:
Subject: question about new fmgr in 7.1 snapshots