| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | albertobruening <albertobruening(at)hotmail(dot)com> |
| Cc: | pgsql-es-ayuda <pgsql-es-ayuda(at)postgresql(dot)org> |
| Subject: | RE: Problemas para Levantar la Base de Datos (SHHMAX) |
| Date: | 2010-12-28 15:29:15 |
| Message-ID: | 1293550016-sup-9330@alvh.no-ip.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-es-ayuda |
Excerpts from albertobruening's message of mar dic 28 11:59:26 -0300 2010:
>
> Este el mensaje en log del postgresql.
>
> could not create shared memory segment: No queda espacio en el dispositivo.
>
> Hint: this error does *not* mean that yoy have run out of disk space. it occurs either if all
> shared memory IDs have been taken, in wich case you need to raise SHMMNI parameter in yout kernel,
> or because the system's overall limit for shared memory has been reached. if you cannot increase
> the shared memory limit, reduce postgresql shared memory request (currently 1103593472 bytes),
> by reducing its shared_buffers parameters (currently 1031072) and/or its max_conexxion parameters
> (currently 100).
En ninguna parte se menciona SHMMAX. Puede ser que el problema sea
SHMALL; o quizás estás pidiendo demasiada memoria, considerando que el
servidor sólo tiene 4 GB. ¿Qué más está corriendo simultáneamente?
Lo de max_connections no creo que tenga nada que ver.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jaime Giraldo | 2010-12-28 15:29:37 | Re: consulta max_connexion... |
| Previous Message | Jaime Giraldo | 2010-12-28 15:23:10 | Re: Problemas para Levantar la Base de Datos (SHHMAX) |