From 5b24a98f2a16fecfc7138d48e38b117e9983a269 Mon Sep 17 00:00:00 2001
From: Bruce Momjian
Date: Thu, 3 Jan 2002 08:13:51 +0000
Subject: Update FAQ_DEV.

---
 doc/FAQ_DEV | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

(limited to 'doc/FAQ_DEV')

diff --git a/doc/FAQ_DEV b/doc/FAQ_DEV
index ef8d90717a0..5aec71f6076 100644
--- a/doc/FAQ_DEV
+++ b/doc/FAQ_DEV
@@ -1,7 +1,7 @@
 
           Developer's Frequently Asked Questions (FAQ) for PostgreSQL
                                        
-   Last updated: Sat Dec 29 23:31:26 EST 2001
+   Last updated: Thu Jan 3 03:13:44 EST 2002
    
    Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
    
@@ -632,11 +632,11 @@ List *i, *list;
   2.5) Why do we use palloc() and pfree() to allocate memory?
   
    palloc() and pfree() are used in place of malloc() and free() because
-   we automatically free all memory allocated when a transaction
-   completes. This makes it easier to make sure we free memory that gets
-   allocated in one place, but only freed much later. There are several
-   contexts that memory can be allocated in, and this controls when the
-   allocated memory is automatically freed by the backend.
+   we find it easier to automatically free all memory allocated when a
+   query completes. This assures us that all memory that was allocated
+   gets freed even if we have lost track of where we allocated it. There
+   are special non-query contexts that memory can be allocated in. These
+   affect when the allocated memory is freed by the backend.
    
   2.6) What is elog()?
   
-- 
cgit v1.2.3