Re: PATCH: backtraces for error messages

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: PATCH: backtraces for error messages
Дата
Msg-id CA+TgmobC8zKGYZiOEZUMWTGcSgKLeNDNU+SCWewXA9pvFWqSKg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: PATCH: backtraces for error messages  (Andres Freund <andres@anarazel.de>)
Список pgsql-hackers
On Wed, Jun 20, 2018 at 1:15 PM, Andres Freund <andres@anarazel.de> wrote:
> I don't think that's ok. It's perfectly possible to hit
> ERRCODE_INTERNAL_ERROR at a high frequency in some situations,

Really?  How?

> and
> there's plenty cases that aren't ERRCODE_INTERNAL_ERROR where we'd want
> this. E.g. a lot of generic filesystem errors have
> errcode_for_file_access(), but are too generic messages to debug.  So I
> think we'll just need a separate GUC for things that aren't PANIC and
> haven't explicitly opt-ed in.

Mmph.  I don't like that much.  I mean I can hold my nose, but I hope
we can find a way to do better.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


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

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: Avoiding Tablespace path collision for primary and standby
Следующее
От: Alexander Korotkov
Дата:
Сообщение: Re: [HACKERS] WIP: long transactions on hot standby feedback replica/ proof of concept