RE: [HACKERS] Patch for elog(FATAL)/elog(ERROR) infinite loop?

From: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
To: "Kristofer Munn" <kmunn(at)munn(dot)com>
Cc: <pgsql-hackers(at)postgreSQL(dot)org>
Subject: RE: [HACKERS] Patch for elog(FATAL)/elog(ERROR) infinite loop?
Date: 2000-01-24 01:01:36
Message-ID: 001f01bf6606$904c0000$2801007e@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> -----Original Message-----
> From: owner-pgsql-hackers(at)postgreSQL(dot)org
> [mailto:owner-pgsql-hackers(at)postgreSQL(dot)org]On Behalf Of Kristofer Munn
>
> Hi everyone. Awhile back I reported the elog(FATAL)/elog(ERROR) infinite
> loop and I see it marked in the TODO as done for 7.0. Is there a patch
> for this problem for 6.5.3?
>

Is your report [HACKERS] ERROR: infinite recursion in proc_exit ?
Is the TODO * -spinlock stuck problem when elog(FATAL) and elog(ERROR)
inside bufmgr ?
The TODO case is different from your problem.

Regards.

Hiroshi Inoue
Inoue(at)tpf(dot)co(dot)jp

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alfred Perlstein 2000-01-24 01:32:54 Re: pg_dump possible fix, need testers. (was: Re: [HACKERS] pg_dump disaster)
Previous Message Hannu Krosing 2000-01-23 22:37:21 Re: [HACKERS] Happy column dropping