Re: elog(PANIC) should abort()? - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: elog(PANIC) should abort()?
Date
Msg-id Pine.LNX.4.44.0211261950030.12428-100000@localhost.localdomain
Whole thread Raw
In response to elog(PANIC) should abort()?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: elog(PANIC) should abort()?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
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.
>
> Going out via proc_exit(), as it now does, seems like a bad idea in any
> case, since that will try to do a bunch of cleanup activity that's
> probably inappropriate after a panic.

But is this appropriate?

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

-- 
Peter Eisentraut   peter_e@gmx.net



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Location of language .mo files or
Next
From: Bruce Momjian
Date:
Subject: Re: [mail] Re: Native Win32 sources