| From: | "Carlos T(dot) Groero Carmona" <ctonetg(at)gmail(dot)com> |
|---|---|
| To: | Lista PostgreSql <pgsql-es-ayuda(at)postgresql(dot)org> |
| Subject: | Urgente, postgres down |
| Date: | 2019-02-07 00:01:20 |
| Message-ID: | CABh6Tc3su1ajbZfeDsJWUaSeD+i1P8H8AnNVmiJMdL6N-jY1qg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-es-ayuda |
Hola,
El servidor de BD se cayo, actualmente caido, tratando de resolverlo..
tratando de ejectutar el vacuum solicitado...responde esto
ERROR: database is not accepting commands to avoid wraparound data loss in
database "db_production" HINT: Stop the postmaster and use a standalone
backend to vacuum that database. You might also need to commit or roll back
old prepared transactions.
siguiendo estos articulos tratando de resolverlo...
https://access.redhat.com/solutions/269323
https://community.arubanetworks.com/t5/Monitoring-Management-Location/Using-a-standalone-backend-to-vacuum-database-quot-postgres-quot/ta-p/169522
pero no puedo conectar al postmaster...any idea..please...
Saliudos
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2019-02-07 00:34:17 | Re: Urgente, postgres down |
| Previous Message | Horacio Miranda | 2019-01-30 08:27:19 | Re: Postgres 10: no se pudo lanzar el nuevo proceso para la conexión: Recurso no disponible temporalmente |