| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | ngaleyev(at)wavelengthmail(dot)com |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: hot restart of posgtresql |
| Date: | 2007-07-04 01:57:20 |
| Message-ID: | 16558.1183514240@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
ngaleyev(at)wavelengthmail(dot)com writes:
> 2007-07-03 19:20:42 EDT 2928 FATAL: could not create shared memory
> segment: Invalid argument
> 2007-07-03 19:20:42 EDT 2928 DETAIL: Failed system call was
> shmget(key=5432001, size=3276259328, 03600).
> 2007-07-03 19:20:42 EDT 2928 HINT: This error usually means that
> PostgreSQL's request for a shared memory segment exceeded your kernel's
> SHMMAX parameter. You can either reduce the request size or reconfigure
> the kernel with larger SHMMAX. To reduce the request size (currently
> 3276259328 bytes), reduce PostgreSQL's shared_buffers parameter (currently
> 393216) and/or its max_connections parameter (currently 250).
> heres my sysctl:
> kernel.shmmax=4294967296
> kernel.shmall=536870912
Why have you got SHMALL set to half a GB when you have Postgres
configured to ask for over 3 GB?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2007-07-04 02:29:44 | Re: hot restart of posgtresql |
| Previous Message | Kawecki_Lewis | 2007-07-04 00:42:27 | Correct configuration to access Postgres 7.3 from remote client? |