From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Thomas Lockhart <lockhart(at)fourpalms(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: elog() proposal |
Date: | 2002-02-25 01:45:40 |
Message-ID: | 200202250145.g1P1jef11309@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > I think FATALALL is good, because it tells you exactly what is going on,
> > namely the same as FATAL but for all sessions.
>
> But it isn't the same. If all backends FATAL'ed at once, that wouldn't
> provoke the postmaster to wipe shared memory and run a WAL recovery
> cycle.
I called it FATALALL because the effect is to have all backends
FATALly terminate.
> What do you think of Karl's suggestion of PANIC?
That is good too. The FATAL becomes like a process segfault, and PANIC
is like a kernel panic.
I don't have a preference. I will let you folks duke it out. :-)
(I guess I lean toward PANIC. Sounds cooler. Not sure that is a good
reason. :-) )
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | pgsql-bugs | 2002-02-25 01:48:14 | Bug #602: Chinese characters query bug. |
Previous Message | Bruce Momjian | 2002-02-25 01:42:15 | Nice Oracle tuning article |