From c0cbb261dfe87f9b55e4e7dd8c6da6eca7e1e22c Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Mon, 25 Feb 2002 20:29:39 +0000
Subject: [PATCH] Update FAQ_DEV.
---
doc/FAQ_DEV | 18 +++++++++++-------
doc/src/FAQ/FAQ_DEV.html | 23 ++++++++++++++---------
2 files changed, 25 insertions(+), 16 deletions(-)
diff --git a/doc/FAQ_DEV b/doc/FAQ_DEV
index 3baa2f492ed..e640766aa5d 100644
--- a/doc/FAQ_DEV
+++ b/doc/FAQ_DEV
@@ -1,7 +1,7 @@
Developer's Frequently Asked Questions (FAQ) for PostgreSQL
- Last updated: Sat Feb 23 15:09:27 EST 2002
+ Last updated: Mon Feb 25 15:29:28 EST 2002
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
@@ -642,12 +642,16 @@ List *i, *list;
elog() is used to send messages to the front-end, and optionally
terminate the current query being processed. The first parameter is an
- elog level of NOTICE, DEBUG, ERROR, or FATAL. NOTICE prints on the
- user's terminal and the postmaster logs. DEBUG prints only in the
- postmaster logs. ERROR prints in both places, and terminates the
- current query, never returning from the call. FATAL terminates the
- backend process. The remaining parameters of elog are a printf-style
- set of parameters to print.
+ elog level of DEBUG (levels 1-5), LOG, INFO, NOTICE, ERROR, FATAL, or
+ PANIC. NOTICE prints on the user's terminal and the postmaster logs.
+ INFO prints only to the user's terminal and LOG prints only to the
+ server logs. (These can be changed from postgresql.conf.) ERROR prints
+ in both places, and terminates the current query, never returning from
+ the call. FATAL terminates the backend process. The remaining
+ parameters of elog are a printf-style set of parameters to print.
+
+ elog(ERROR) frees most memory and open file descriptors so you don't
+ need to clean these up before the call.
2.7) What is CommandCounterIncrement()?
diff --git a/doc/src/FAQ/FAQ_DEV.html b/doc/src/FAQ/FAQ_DEV.html
index 3af3b7d200c..9e557284b31 100644
--- a/doc/src/FAQ/FAQ_DEV.html
+++ b/doc/src/FAQ/FAQ_DEV.html
@@ -12,7 +12,7 @@
<H1>Developer's Frequently Asked Questions (FAQ) for
PostgreSQL</H1>
- <P>Last updated: Sat Feb 23 15:09:27 EST 2002</P>
+ <P>Last updated: Mon Feb 25 15:29:28 EST 2002</P>
<P>Current maintainer: Bruce Momjian (<A href=
"mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR>
@@ -777,14 +777,19 @@
<P><I>elog()</I> is used to send messages to the front-end, and
optionally terminate the current query being processed. The first
- parameter is an elog level of <I>NOTICE,</I> <I>DEBUG,</I>
- <I>ERROR,</I> or <I>FATAL.</I> <I>NOTICE</I> prints on the user's
- terminal and the postmaster logs. <I>DEBUG</I> prints only in the
- postmaster logs. <I>ERROR</I> prints in both places, and terminates
- the current query, never returning from the call. <I>FATAL</I>
- terminates the backend process. The remaining parameters of
- <I>elog</I> are a <I>printf</I>-style set of parameters to
- print.</P>
+ parameter is an elog level of <I>DEBUG</I> (levels 1-5), <I>LOG,</I>
+ <I>INFO,</I> <I>NOTICE,</I> <I>ERROR,</I> <I>FATAL,</I> or
+ <I>PANIC.</I> <I>NOTICE</I> prints on the user's terminal and the
+ postmaster logs. <I>INFO</I> prints only to the user's terminal and
+ <I>LOG</I> prints only to the server logs. (These can be changed
+ from <I>postgresql.conf.</I>) <I>ERROR</I> prints in both places,
+ and terminates the current query, never returning from the call.
+ <I>FATAL</I> terminates the backend process. The remaining
+ parameters of <I>elog</I> are a <I>printf</I>-style set of
+ parameters to print.</P>
+
+ <P><I>elog(ERROR)</I> frees most memory and open file descriptors so
+ you don't need to clean these up before the call.</P>
<H3><A name="2.7">2.7</A>) What is CommandCounterIncrement()?</H3>
--
GitLab