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
94cb2201
Commit
94cb2201
authored
23 years ago
by
Bruce Momjian
Browse files
Options
Downloads
Patches
Plain Diff
Update FAQ.
parent
88e94821
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
doc/FAQ
+5
-4
5 additions, 4 deletions
doc/FAQ
doc/src/FAQ/FAQ.html
+5
-4
5 additions, 4 deletions
doc/src/FAQ/FAQ.html
with
10 additions
and
8 deletions
doc/FAQ
+
5
−
4
View file @
94cb2201
Frequently Asked Questions (FAQ) for PostgreSQL
Frequently Asked Questions (FAQ) for PostgreSQL
Last updated:
Sat
Jun
9 10:40:33
EDT 2001
Last updated:
Mon
Jun
11 12:27:44
EDT 2001
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
...
@@ -900,9 +900,10 @@ BYTEA bytea variable-length byte array (null-safe)
...
@@ -900,9 +900,10 @@ BYTEA bytea variable-length byte array (null-safe)
4.19) Why do I get the error "ERROR: Memory exhausted in AllocSetAlloc()?"
4.19) Why do I get the error "ERROR: Memory exhausted in AllocSetAlloc()?"
It is possible you have run out of virtual memory on your system, or
If you are running a version older than 7.1, an upgrade may fix the
your kernel has a low limit for certain resources. Try this before
problem. Also it is possible you have run out of virtual memory on
starting the postmaster:
your system, or your kernel has a low limit for certain resources. Try
this before starting the postmaster:
ulimit -d 262144
ulimit -d 262144
limit datasize 256m
limit datasize 256m
...
...
This diff is collapsed.
Click to expand it.
doc/src/FAQ/FAQ.html
+
5
−
4
View file @
94cb2201
...
@@ -12,7 +12,7 @@
...
@@ -12,7 +12,7 @@
alink=
"#0000FF"
>
alink=
"#0000FF"
>
<H1>
Frequently Asked Questions (FAQ) for PostgreSQL
</H1>
<H1>
Frequently Asked Questions (FAQ) for PostgreSQL
</H1>
<P>
Last updated:
Sat
Jun
9 10:40:33
EDT 2001
</P>
<P>
Last updated:
Mon
Jun
11 12:27:44
EDT 2001
</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>
...
@@ -1155,9 +1155,10 @@ BYTEA bytea variable-length byte array (null-safe)
...
@@ -1155,9 +1155,10 @@ BYTEA bytea variable-length byte array (null-safe)
Memory exhausted in AllocSetAlloc()?"
</I><BR>
Memory exhausted in AllocSetAlloc()?"
</I><BR>
</H4>
</H4>
<P>
It is possible you have run out of virtual memory on your
<P>
If you are running a version older than 7.1, an upgrade may fix
system, or your kernel has a low limit for certain resources. Try
the problem. Also it is possible you have run out of virtual memory
this before starting the
<I>
postmaster:
</I></P>
on your system, or your kernel has a low limit for certain resources.
Try this before starting the
<I>
postmaster:
</I></P>
<PRE>
<PRE>
ulimit -d 262144
ulimit -d 262144
limit datasize 256m
limit datasize 256m
...
...
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