Re: warning en bd

From: Miguel Angel Hernandez Moreno <miguel(dot)hdz(dot)mrn(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Lista PostgreSql <pgsql-es-ayuda(at)postgresql(dot)org>
Subject: Re: warning en bd
Date: 2010-11-15 15:13:05
Message-ID: AANLkTi==4Kh72jzD33B961heJgVRGp0J1nwhQyVy8qxy@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-es-ayuda

ok!!

creo k llegue muy tarde a todo esto porque ya no9 me deja ni hacer un
sencillo
insert, quice hacer el vacuum como dice alvaro y me marca lo siguiente

*INFO: vacuuming "pg_catalog.pg_type"INFO: "pg_type": found 0 removable,
972 nonremovable row versions in 39793 pages
DETAIL: 0 dead row versions cannot be removed yet.
Nonremovable row versions range from 168 to 652 bytes long.
There were 1516495 unused item pointers.
Total free space (including removable row versions) is 318795564 bytes.
39738 pages are or will become empty, including 28 at the end of the table.
39752 pages containing 318574388 free bytes are potential move destinations.
CPU 0.00s/0.06u sec elapsed 0.09 sec.INFO: index "pg_type_oid_index" now
contains 972 row versions in 18789 pages
DETAIL: 2 index row versions were removed.
18646 index pages have been deleted, 17823 are currently reusable.
CPU 0.16s/0.03u sec elapsed 1.92 sec.INFO: index
"pg_type_typname_nsp_index" now contains 972 row versions in 4961 pages
DETAIL: 2 index row versions were removed.
4844 index pages have been deleted, 4455 are currently reusable.
CPU 0.04s/0.00u sec elapsed 0.58 sec.ERROR: database is not accepting
commands to avoid wraparound data loss in database "feria"
HINT: Stop the postmaster and use a standalone backend to vacuum database
"feria".
You might also need to commit or roll back old prepared transactions.

ERROR: database is not accepting commands to avoid wraparound data loss in
database "feria"
HINT: Stop the postmaster and use a standalone backend to vacuum database
"feria".
You might also need to commit or roll back old prepared transactions.*

creo que ahora si es necesario la conexion sencilla, pero sigue sin dejarme
entrar
con la siguiente sentencia
*postgres --single -D /var/lib/pgsql/datos/ postgres*

ahora si "ni pa delante ni pa tras" como dirian en mi rancho!!!

2010/11/15 Alvaro Herrera <alvherre(at)commandprompt(dot)com>

> Excerpts from Miguel Angel Hernandez Moreno's message of lun nov 15
> 09:15:04 -0300 2010:
> > hola lista
> >
> > buen dia, fijense que estaba haciendo los respaldos correspondientes de
> > la base de datos pero ahora cuando levante los procesos de acceso
> > en las aplicaciones me erroja el siguiente warning
> >
> > *WARNING: database "feria" must be vacuumed within 4717394 transactions
> > HINT: To avoid a database shutdown, execute a database-wide VACUUM in
> > "feria".
>
> No necesitas entrar en forma "sencilla". Simplemente conectate a la
> base de datos feria y ejecuta VACUUM. Si falla en alguna tabla por
> cualquier motivo, debes investigar eso.
>
> --
> Álvaro Herrera <alvherre(at)commandprompt(dot)com>
> The PostgreSQL Company - Command Prompt, Inc.
> PostgreSQL Replication, Consulting, Custom Development, 24x7 support
>

--
ISC Miguel Angel Hernandez Moreno

In response to

Responses

Browse pgsql-es-ayuda by date

  From Date Subject
Next Message Alvaro Herrera 2010-11-15 15:53:13 Re: warning en bd
Previous Message Jaime Casanova 2010-11-15 15:05:15 Re: [pgsql-es-ayuda] Mejor distribución de discos para Postgre?