Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
P
postgres-lambda-diff
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Jakob Huber
postgres-lambda-diff
Commits
5b24a98f
Commit
5b24a98f
authored
23 years ago
by
Bruce Momjian
Browse files
Options
Downloads
Patches
Plain Diff
Update FAQ_DEV.
parent
9c00d0de
No related branches found
No related tags found
No related merge requests found
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
doc/FAQ_DEV
+6
-6
6 additions, 6 deletions
doc/FAQ_DEV
doc/src/FAQ/FAQ_DEV.html
+7
-7
7 additions, 7 deletions
doc/src/FAQ/FAQ_DEV.html
with
13 additions
and
13 deletions
doc/FAQ_DEV
+
6
−
6
View file @
5b24a98f
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 200
1
Last updated:
Thu Jan 3 03:13:44
EST 200
2
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;
...
@@ -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 th
e
are special non-query
contexts that memory can be allocated in
. Thes
e
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()?
...
...
This diff is collapsed.
Click to expand it.
doc/src/FAQ/FAQ_DEV.html
+
7
−
7
View file @
5b24a98f
...
@@ -12,7 +12,7 @@
...
@@ -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 200
1
</P>
<P>
Last updated:
Thu Jan 3 03:13:44
EST 200
2
</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 @@
...
@@ -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
get
s allocated
in one place, but only freed much later.
memory that
wa
s allocated
gets freed even if we have lost track of
T
here
are several contexts that memory can be allocated in, and
w
here
we allocated it. There are special non-query contexts that
this controls when the allocated memory is automatically freed b
y
memory can be allocated in. These affect when the allocated memor
y
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>
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment