Re: A couple items on TODO - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: A couple items on TODO
Date
Msg-id Pine.LNX.4.30.0108232053430.677-100000@peter.localdomain
Whole thread Raw
In response to Re: A couple items on TODO  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane writes:

> AFAIR, elog at NOTICE or DEBUG level isn't really supposed to have any
> side-effects.  The bigger issue is that you have to be careful about
> using it in certain places, mainly during startup or for reporting
> communication errors.  (send failure -> elog -> tries to send message to
> client -> send failure -> elog -> trouble)

It's especially postmaster.c and the related subroutines elsewhere that
I'm not happy about.  The postmaster would really need a way to report an
error to the log and continue in its merry ways.  This could probably be
encapsulated in elog() by setting a flag variable "I'm the postmaster" --
might even exit already.  Note:  In my experience, the previous suggestion
to return to the postmaster main loop on error would not really be useful.

-- 
Peter Eisentraut   peter_e@gmx.net   http://funkturm.homeip.net/~peter



pgsql-hackers by date:

Previous
From: Christopher Masto
Date:
Subject: Re: Escaping strings for inclusion into SQL queries
Next
From: Tom Lane
Date:
Subject: Re: [JDBC] New backend functions? [was Re: JDBC changes for 7.2... some questions...]