From: | Doug Hall <doughalldev(at)gmail(dot)com> |
---|---|
To: | psql novice <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: Help! Not enough swap space? |
Date: | 2005-07-13 21:26:01 |
Message-ID: | 6ecb817005071314265919d0ab@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Oops. Apparently, this is what happens when you forget to shut down
the old postmaster first. :-/
On 7/13/05, Doug Hall <doughalldev(at)gmail(dot)com> wrote:
> When I perform an initdb, I get the following error.
<SNIP>
> creating directory data/pg_tblspc ... ok
> selecting default max_connections ... 10
> selecting default shared_buffers ... 50
> creating configuration files ... ok
> creating template1 database in data/base/1 ... FATAL: could not create
> shared memory segment: Cannot allocate memory
> DETAIL: Failed system call was shmget(key=1, size=1122304, 03600).
> HINT: This error usually means that PostgreSQL's request for a shared
> memory segment exceeded available memory or swap space. To reduce the
> request size (currently 1122304 bytes), reduce PostgreSQL's
> shared_buffers parameter (currently 50) and/or its max_connections
> parameter (currently 10).
> The PostgreSQL documentation contains more information about
> shared memory configuration.
> child process exited with exit code 1
> initdb: removing contents of data directory "data"
> mu160:/usr/local/pgsql postgres$
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-07-13 22:04:36 | Re: Help! Not enough swap space? |
Previous Message | Diana Nemirovsky | 2005-07-13 20:46:52 | plpgsql trigger problem |