Re: [HACKERS] MergeJoin and Mark/Restr scan positions (Re: [PORTS] Port Bug Report)

Поиск
Список
Период
Сортировка
От Vadim B. Mikheev
Тема Re: [HACKERS] MergeJoin and Mark/Restr scan positions (Re: [PORTS] Port Bug Report)
Дата
Msg-id 34F62D68.5C655710@sable.krasnoyarsk.su
обсуждение исходный текст
Ответ на Re: [HACKERS] MergeJoin and Mark/Restr scan positions (Re: [PORTS] Port Bug Report)  (Bruce Momjian <maillist@candle.pha.pa.us>)
Список pgsql-hackers
Bruce Momjian wrote:
>
> > BTW, elog(FATAL) from vacuum and btree were reported by 2-3
> > another ppl - shouldn't we ask users to re-compile server with
> > CASSERT in all "FATAL" cases ?
> > CASSERT assisted me very much to find real sources of this problem
> > and recently fixed vacuum bug.
>
> I am a little confused on when we should have them use this.  In most
> cases, turning on CASSERT doesn't help.  Should we suggest it in certain
> cases as we see it applies, or is there a rule we can give them to tell
> them when to try it?

For me, CASSERT is last chance to put me in right direction when
I can't reproduce reported bug (user can't provide test data etc).
But you're right - we shouldn't suggest anything generaly.

BTW, Alvin got ASSERTion for real data! We'll try to fix this...

Vadim

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

Предыдущее
От: "Michael J. Rogan"
Дата:
Сообщение: Re: [HACKERS] sequences
Следующее
От: "Thomas G. Lockhart"
Дата:
Сообщение: Re: [HACKERS] Re: Postgresql broken