database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-10 09:21:54 +03:00
Code

Update FAQ_DEV.

Browse Source
This commit is contained in:
Bruce Momjian 2002-01-03 08:13:51 +00:00
parent 9c00d0de57
commit 5b24a98f2a
2 changed files with 13 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/FAQ_DEV
View File

@ -1,7 +1,7 @@
Developer's Frequently Asked Questions (FAQ) for PostgreSQL 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) 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? 2.5) Why do we use palloc() and pfree() to allocate memory?
palloc() and pfree() are used in place of malloc() and free() because palloc() and pfree() are used in place of malloc() and free() because
we automatically free all memory allocated when a transaction we find it easier to automatically free all memory allocated when a
completes. This makes it easier to make sure we free memory that gets query completes. This assures us that all memory that was allocated
allocated in one place, but only freed much later. There are several gets freed even if we have lost track of where we allocated it. There
contexts that memory can be allocated in, and this controls when the are special non-query contexts that memory can be allocated in. These
allocated memory is automatically freed by the backend. affect when the allocated memory is freed by the backend.
2.6) What is elog()? 2.6) What is elog()?

14
doc/src/FAQ/FAQ_DEV.html
View File

@ -12,7 +12,7 @@
<H1>Developer's Frequently Asked Questions (FAQ) for <H1>Developer's Frequently Asked Questions (FAQ) for
PostgreSQL</H1> PostgreSQL</H1>
<P>Last updated: Sat Dec 29 23:31:26 EST 2001</P> <P>Last updated: Thu Jan 3 03:13:44 EST 2002</P>
<P>Current maintainer: Bruce Momjian (<A href= <P>Current maintainer: Bruce Momjian (<A href=
"mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR> "mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR>
@ -766,12 +766,12 @@
<I>pfree</I>() to allocate memory?</H3> <I>pfree</I>() to allocate memory?</H3>
<P><I>palloc()</I> and <I>pfree()</I> are used in place of malloc() <P><I>palloc()</I> and <I>pfree()</I> are used in place of malloc()
and free() because we automatically free all memory allocated when and free() because we find it easier to automatically free all
a transaction completes. This makes it easier to make sure we free memory allocated when a query completes. This assures us that all
memory that gets allocated in one place, but only freed much later. memory that was allocated gets freed even if we have lost track of
There are several contexts that memory can be allocated in, and where we allocated it. There are special non-query contexts that
this controls when the allocated memory is automatically freed by memory can be allocated in. These affect when the allocated memory
the backend.</P> is freed by the backend.</P>
<H3><A name="2.6">2.6</A>) What is elog()?</H3> <H3><A name="2.6">2.6</A>) What is elog()?</H3>