Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit5b24a98

Browse files
committed
Update FAQ_DEV.
1 parent9c00d0d commit5b24a98

File tree

2 files changed

+13
-13
lines changed

2 files changed

+13
-13
lines changed

‎doc/FAQ_DEV

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11

22
Developer's Frequently Asked Questions (FAQ) for PostgreSQL
33

4-
Last updated:Sat Dec 29 23:31:26 EST2001
4+
Last updated:Thu Jan 3 03:13:44 EST2002
55

66
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
77

@@ -632,11 +632,11 @@ List *i, *list;
632632
2.5) Why do we use palloc() and pfree() to allocate memory?
633633

634634
palloc() and pfree() are used in place of malloc() and free() because
635-
we automatically free all memory allocated when a transaction
636-
completes. Thismakes it easier to make sure we freememory thatgets
637-
allocated in one place, but only freed much later. There are several
638-
contexts that memory can be allocated in, and this controls when the
639-
allocated memory is automatically freed by the backend.
635+
wefind it easier toautomatically free all memory allocated when a
636+
querycompletes. Thisassures us that allmemory thatwas allocated
637+
gets freed even if we have lost track of where we allocated it. There
638+
are special non-querycontexts that memory can be allocated in. These
639+
affect when theallocated memory is freed by the backend.
640640

641641
2.6) What is elog()?
642642

‎doc/src/FAQ/FAQ_DEV.html

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@
1212
<H1>Developer's Frequently Asked Questions (FAQ) for
1313
PostgreSQL</H1>
1414

15-
<P>Last updated:Sat Dec 29 23:31:26 EST2001</P>
15+
<P>Last updated:Thu Jan 3 03:13:44 EST2002</P>
1616

1717
<P>Current maintainer: Bruce Momjian (<Ahref=
1818
"mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR>
@@ -766,12 +766,12 @@ <H3><A name="2.5">2.5</A>) Why do we use <I>palloc</I>() and
766766
<I>pfree</I>() to allocate memory?</H3>
767767

768768
<P><I>palloc()</I> and<I>pfree()</I> are used in place of malloc()
769-
and free() because weautomatically free all memory allocated when
770-
a transaction completes. Thismakes it easier to make sure we free
771-
memory thatgets allocatedin one place, but only freed much later.
772-
There are several contexts that memory can be allocated in, and
773-
this controls when theallocatedmemory is automatically freed by
774-
the backend.</P>
769+
and free() because wefind it easier to automatically free all
770+
memory allocated when a query completes. Thisassures us that all
771+
memory thatwas allocatedgets freed even if we have lost track of
772+
where we allocated it. There are special non-query contexts that
773+
memory can beallocatedin. These affect when the allocated memory
774+
is freed bythe backend.</P>
775775

776776
<H3><Aname="2.6">2.6</A>) What is elog()?</H3>
777777

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp