Re: 8.3.0 backend segfaults

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: 8.3.0 backend segfaults
Дата
Msg-id 13629.1205304280@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: 8.3.0 backend segfaults  ("Alex Hunsaker" <badalex@gmail.com>)
Ответы Re: 8.3.0 backend segfaults  ("Alex Hunsaker" <badalex@gmail.com>)
Список pgsql-bugs
"Alex Hunsaker" <badalex@gmail.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?

            regards, tom lane

В списке pgsql-bugs по дате отправления:

Предыдущее
От: "Alex Hunsaker"
Дата:
Сообщение: Re: 8.3.0 backend segfaults
Следующее
От: Peter Eisentraut
Дата:
Сообщение: Re: BUG #4027: backslash escaping not disabled in plpgsql