Re: elog(PANIC) should abort()?

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Tom Lane writes:
>> I am thinking it would be useful for debugging if elog(PANIC) were to
>> exit by calling abort() so that a core dump would be produced.

> But is this appropriate?

> PANIC: The database cluster was initialized with CATALOG_VERSION_NO 200210181,
> but the backend was compiled with CATALOG_VERSION_NO 200211021.
> It looks like you need to initdb.
> Aborted (core dumped)

Hm. We could possibly reduce those particular messages to FATAL.

OTOH, it's not unreasonable that seeing those messages *in the field*
might be an appropriate situation for a core dump. I think as
developers we sometimes have a skewed sense of what's common ;-)

Ever since Bruce introduced the additional elog levels, I have felt it
would be a good idea to go through all the elog calls and re-evaluate
what levels they should have. It's a lot o' work though...

regards, tom lane