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 19:37:59
Message-ID: 29052.1205350679@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Alex Hunsaker" <badalex(at)gmail(dot)com> writes:
> Perhaps my simple updates are not enough for analyze to
> invalidate the query plan? Should I be doing inserts/deletes or just
> more updates?

No, AFAICS the plan inval will happen after a vacuum regardless of whether
anything actually changed. I'm thinking that there's some property
of the query or the invoked function that's relevant, but it's not
clear what. (We'll know soon enough once we can reproduce it easily...)

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alex Hunsaker 2008-03-12 19:59:42 Re: 8.3.0 backend segfaults
Previous Message Bruce Momjian 2008-03-12 19:37:00 Re: BUG #4027: backslash escaping not disabled in plpgsql