Re: elog() proposal - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: elog() proposal
Date
Msg-id 200202230020.g1N0KBQ09567@candle.pha.pa.us
Whole thread Raw
In response to Re: elog() proposal  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: elog() proposal  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> Oh, now I get the point: you want to not pick up debug-level messages
> for translation at all.  That makes sense.  Okay, how about we take
> the names Bruce was proposing and make them function names:
> 
>     PGLog(msg, ...)
>     PGError(msg, ...)
>     PGCrash(msg, ...)

OK, so elog(ERROR, ...) and PGError(msg, ...) would be the same.  Makes
sense.  Should we consider hiding these in macros so they really still
call elog(ERROR, ...) for backward compatiblity?

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: elog() proposal
Next
From: Tom Lane
Date:
Subject: Re: Storage Location Patch Proposal for V7.3