Re: 8.3.0 backend segfaults - Mailing list pgsql-bugs

From Tom Lane
Subject Re: 8.3.0 backend segfaults
Date
Msg-id 19766.1205336985@sss.pgh.pa.us
Whole thread Raw
In response to Re: 8.3.0 backend segfaults  ("Alex Hunsaker" <badalex@gmail.com>)
Responses Re: 8.3.0 backend segfaults
List pgsql-bugs
"Alex Hunsaker" <badalex@gmail.com> writes:
> On Wed, Mar 12, 2008 at 12:44 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> 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.

Yeah, I was going to suggest that you ought to be able to extract
a test case involving doing a manual vacuum in between prepare and
execute.  I suspect it wouldn't even need to involve more than one
session.

            regards, tom lane

pgsql-bugs by date:

Previous
From: "Alex Hunsaker"
Date:
Subject: Re: 8.3.0 backend segfaults
Next
From: "Alex Hunsaker"
Date:
Subject: Re: 8.3.0 backend segfaults