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

Re: 8.3.0 backend segfaults

From: "Alex Hunsaker" <badalex(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: 8.3.0 backend segfaults
Date: 2008-03-12 15:42:08
Message-ID: 34d269d40803120842l31efdf12t7965e286af562e2b@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
On Wed, Mar 12, 2008 at 12:44 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Alex Hunsaker" <badalex(at)gmail(dot)com> writes:
>
> > the mean time here is a new backtrace I just got (lord knows how... it
>  > seems to be as soon as I stop trying to make it crash and look away,
>  > thats when it does).
>
>  Not sure that you are clear on what's happening here, but the train of
>  events is something like
>         - you prepare a statement
>         - somebody modifies the schema of one of the tables used in the
>           statement
>         - you try to execute the statement, and updating the prepared
>           plan crashes
>
>  If you say "none of my stuff is changing any schemas", then I'd guess
>  that the triggering event is a background autovacuum, which forces
>  replan just like an intentional schema change would.  Does stopping
>  autovacuum make the problem go away?

Yep turning off autovacuum seems to have fixed it.  And once I
manually vacuum analyze workers; it blows up almost instantly.

In response to

Responses

pgsql-bugs by date

Next:From: Alex HunsakerDate: 2008-03-12 15:44:58
Subject: Re: 8.3.0 backend segfaults
Previous:From: Tom LaneDate: 2008-03-12 15:39:14
Subject: Re: 8.3.0 backend segfaults

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