Dear all, First of all i wish to share actual error meassge, Below are the queries i had executed on the terminal on my server
-bash-3.2$ touch fix.sql -bash-3.2$ echo "VACUUM FULL;" > fix.sql -bash-3.2$ postgres -D /var/lib/pgsql/data patnadbold < fix.sql WARNING: database "patnadbold" must be vacuumed within 1000000 transactions HINT: To avoid a database shutdown, execute a full-database VACUUM in "patnadbold". WARNING: database "patnadbold" must be vacuumed within 1000000 transactions HINT: To avoid a database shutdown, execute a full-database VACUUM in "patnadbold". PostgreSQL stand-alone backend 8.1.11 backend> WARNING: database "patnadbold" must be vacuumed within 999999 transactions HINT: To avoid a database shutdown, execute a full-database VACUUM in "patnadbold". WARNING: database "patnadbold" must be vacuumed within 999998 transactions HINT: To avoid a database shutdown, execute a full-database VACUUM in "patnadbold". WARNING: database "patnadbold" must be vacuumed within 999997 transactions HINT: To avoid a database shutdown, execute a full-database VACUUM in "patnadbold". WARNING: database "patnadbold" must be vacuumed within 999996 transactions HINT: To avoid a database shutdown, execute a full-database VACUUM in "patnadbold". WARNING: database "patnadbold" must be vacuumed within 999995 transactions HINT: To avoid a database shutdown, execute a full-database VACUUM in "patnadbold". WARNING: database "patnadbold" must be vacuumed within 999994 transactions HINT: To avoid a database shutdown, execute a full-database VACUUM in "patnadbold". WARNING: database "patnadbold" must be vacuumed within 999993 transactions HINT: To avoid a database shutdown, execute a full-database VACUUM in "patnadbold". WARNING: database "patnadbold" must be vacuumed within 999992 transactions HINT: To avoid a database shutdown, execute a full-database VACUUM in "patnadbold". WARNING: database "patnadbold" must be vacuumed within 999991 transactions HINT: To avoid a database shutdown, execute a full-database VACUUM in "patnadbold". WARNING: database "patnadbold" must be vacuumed within 999990 transactions HINT: To avoid a database shutdown, execute a full-database VACUUM in "patnadbold". WARNING: database "patnadbold" must be vacuumed within 999989 transactions HINT: To avoid a database shutdown, execute a full-database VACUUM in "patnadbold". WARNING: database "patnadbold" must be vacuumed within 999988 transactions HINT: To avoid a database shutdown, execute a full-database VACUUM in "patnadbold". WARNING: database "patnadbold" must be vacuumed within 999987 transactions HINT: To avoid a database shutdown, execute a full-database VACUUM in "patnadbold". WARNING: database "patnadbold" must be vacuumed within 999986 transactions HINT: To avoid a database shutdown, execute a full-database VACUUM in "patnadbold". WARNING: database "patnadbold" must be vacuumed within 999985 transactions HINT: To avoid a database shutdown, execute a full-database VACUUM in "patnadbold". WARNING: database "patnadbold" must be vacuumed within 999984 transactions HINT: To avoid a database shutdown, execute a full-database VACUUM in "patnadbold". ERROR: could not access status of transaction 33011 DETAIL: could not open file "pg_clog/0000": No such file or directory exit After this i am able to stop /start my db server but i am not able to connect to my databases (it tells to run vacuum full first on patnadbold databases) 1)I am using postgres 8.4 version. 2) I had two databases on this server i) patnadbold ii) patnaonlinedb For me patnadbold is of no use if at this moment i lost this database that also fine to me. I wanted to connect patnaonlinedb any how and wanted to perform backup of this , Solution please. On Tue, Oct 8, 2013 at 6:19 PM, Adrian Klaver <adrian.kla...@gmail.com>wrote: > On 10/08/2013 03:55 AM, shailesh singh wrote: > >> I had got this message while running vacuum full from backend . Now My >> database is not starting , Help pls. >> >> backend> vacuum full debug; >> WARNING: database "debug" must be vacuumed within 999999 transactions >> HINT: To avoid a database shutdown, execute a full-database VACUUM in >> "debug". >> ERROR: relation "debug" does not exist >> > > >> Now what? >> > > First some information. > > 1) What version of Postgres are you using? > > 2) Does database debug in fact exist or not? > In other words does it show up with \l in psql? > > Also it not necessary to use FULL with the VACUUM. > > > >> Thanks in advance. >> >> Shailesh Singh >> > > > -- > Adrian Klaver > adrian.kla...@gmail.com > -- With Regards, शैलेश सिंह |Shailesh Singh +९१-९६५०३१७५१७ | +91-9650317517
