Re: [HACKERS] elog() executed by postmaster

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: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] elog() executed by postmaster
Date: 1999-11-15 00:48:17
Message-ID: 199911150048.TAA07293@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> elog() should probably check for being in the postmaster and force
> a postmaster shutdown if it gets elog(FATAL). Should elog(ERROR)
> do the same, or do we want to try to add a return-to-main-loop
> capability in the postmaster? I'm inclined to keep it simple and
> just do an orderly shutdown in both cases. Any such code paths that
> are out there are obviously not heavily exercised, so I doubt that
> it's worth adding new code to try to recover from elog(ERROR).

Agreed. Just try simple first.

--
Bruce Momjian | http://www.op.net/~candle
maillist(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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Lamar Owen 1999-11-15 17:12:47 Re: [HACKERS] Looks like hell, but ...
Previous Message Tom Lane 1999-11-14 23:37:22 elog() executed by postmaster