| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Alex Hunsaker" <badalex(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: 8.3.0 backend segfaults |
| Date: | 2008-03-12 15:49:45 |
| Message-ID: | 19766.1205336985@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"Alex Hunsaker" <badalex(at)gmail(dot)com> writes:
> On Wed, Mar 12, 2008 at 12:44 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Hunsaker | 2008-03-12 15:58:02 | Re: 8.3.0 backend segfaults |
| Previous Message | Alex Hunsaker | 2008-03-12 15:44:58 | Re: 8.3.0 backend segfaults |