rdelaage/postgresql
1
0
Fork 0
mirror of https://git.postgresql.org/git/postgresql.git synced 2024-10-01 05:51:14 +02:00
Code Issues Packages Projects Releases Wiki Activity

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
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()?

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

@ -12,7 +12,7 @@
<H1>Developer's Frequently Asked Questions (FAQ) for
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=
"mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR>
@ -766,12 +766,12 @@
<I>pfree</I>() to allocate memory?</H3>
<P><I>palloc()</I> and <I>pfree()</I> 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.</P>
and free() because 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.</P>
<H3><A name="2.6">2.6</A>) What is elog()?</H3>