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

Re: 8.3.0 backend segfaults

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 06:44:40
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
"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
	- 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?

			regards, tom lane

In response to


pgsql-bugs by date

Next:From: Peter EisentrautDate: 2008-03-12 06:54:09
Subject: Re: BUG #4027: backslash escaping not disabled in plpgsql
Previous:From: Alex HunsakerDate: 2008-03-12 06:34:42
Subject: Re: 8.3.0 backend segfaults

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