Re: elog(PANIC) should abort()?

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: elog(PANIC) should abort()?
Date: 2002-11-26 18:50:51
Message-ID: Pine.LNX.4.44.0211261950030.12428-100000@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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_NO 200211021.
It looks like you need to initdb.
Aborted (core dumped)

--
Peter Eisentraut peter_e(at)gmx(dot)net

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Kings-Lynne 2002-11-26 18:51:04 Re: PostGres and WIN32, a plea!
Previous Message scott.marlowe 2002-11-26 18:46:27 Re: performance of insert/delete/update