Re: PANIC :Call AbortTransaction when transaction id is no normal

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: PANIC :Call AbortTransaction when transaction id is no normal
Дата
Msg-id 13093.1557804531@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re:Re: PANIC :Call AbortTransaction when transaction id is nonormal  (Thunder <thunder1@126.com>)
Ответы Re: PANIC :Call AbortTransaction when transaction id is no normal  (Michael Paquier <michael@paquier.xyz>)
Список pgsql-hackers
[ please don't top-post on the PG lists ]

Thunder  <thunder1@126.com> writes:
> At 2019-05-14 07:53:36, "Michael Paquier" <michael@paquier.xyz> wrote:
>> On Mon, May 13, 2019 at 09:37:32AM -0400, Tom Lane wrote:
>>> But ... that code's been like that for decades and nobody's complained
>>> before.  Why are we worried about bootstrap's response to signals at all?

> On our server when process crash and core dump file generated we will receive complaining phone call.
> That's why i try to fix it.

OK, that's fair.  The SIG_DFL change I suggested will fix that problem
for SIGINT etc (except SIGQUIT, for which you should be *expecting*
a core file).  I agree with Michael that we do not wish to change what
happens for an internal error; but external signals do not represent
a bug in PG, so forcing a PANIC for those seems unwarranted.

            regards, tom lane



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

Предыдущее
От: Peter Geoghegan
Дата:
Сообщение: Re: VACUUM can finish an interrupted nbtree page split -- is that okay?
Следующее
От: Tom Lane
Дата:
Сообщение: Re: VACUUM can finish an interrupted nbtree page split -- is that okay?