From d63790d72605cb84fd9e79334ab9d0a5e01378dc Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Tue, 9 Oct 2007 01:28:24 +0000 Subject: Clarify user of "postmaster" vs. "server" in FAQs. Brendan Jurd --- doc/src/FAQ/FAQ.html | 8 ++++---- doc/src/FAQ/FAQ_DEV.html | 6 +++--- 2 files changed, 7 insertions(+), 7 deletions(-) (limited to 'doc/src') diff --git a/doc/src/FAQ/FAQ.html b/doc/src/FAQ/FAQ.html index 7a10b56d9c..cc461f89d5 100644 --- a/doc/src/FAQ/FAQ.html +++ b/doc/src/FAQ/FAQ.html @@ -577,11 +577,11 @@
You have reached the default limit is 100 database sessions. You - need to increase the postmaster's limit on how many +
You have reached the default limit of 100 database sessions. You + need to increase the server's limit on how many concurrent backend processes it can start by changing the max_connections value in postgresql.conf and - restarting the postmaster.
+ restarting the server.You probably have run out of virtual memory on your system, or your kernel has a low limit for certain resources. Try this - before starting postmaster:
+ before starting the server:ulimit -d 262144 limit datasize 256m diff --git a/doc/src/FAQ/FAQ_DEV.html b/doc/src/FAQ/FAQ_DEV.html index 104e68591d..76e22142ec 100644 --- a/doc/src/FAQ/FAQ_DEV.html +++ b/doc/src/FAQ/FAQ_DEV.html @@ -939,7 +939,7 @@ (gdb) call pprint(any_pointer)- The output appears in the postmaster log file, or on your screen if + The output appears in the server log file, or on your screen if you are running a backend directly without a postmaster.
The postmaster has a -d option that allows +
The postgres server has a -d option that allows even more detailed information to be reported. The -d option takes a number that specifies the debug level. Be warned that high debug level values generate large log files.
-- cgit v1.2.3