Urgent Help Required

Поиск
Список
Период
Сортировка
От shailesh singh
Тема Urgent Help Required
Дата
Msg-id CAAzPmNxfDrV72wDmBEv5tcQOByE_wvGSeqRkQj0FizXmCYyaPQ@mail.gmail.com
обсуждение исходный текст
Ответы Re: [GENERAL] Urgent Help Required  (Adrian Klaver <adrian.klaver@gmail.com>)
Re: Urgent Help Required  (Robert Haas <robertmhaas@gmail.com>)
Re: Urgent Help Required  (Jim Nasby <jim@nasby.net>)
Список pgsql-hackers
Дерево обсуждения
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
backend> vacuum full;
WARNING:  database "debug" must be vacuumed within 999998 transactions
HINT:  To avoid a database shutdown, execute a full-database VACUUM in "debug".
WARNING:  database "debug" must be vacuumed within 999997 transactions
HINT:  To avoid a database shutdown, execute a full-database VACUUM in "debug".
WARNING:  database "debug" must be vacuumed within 999996 transactions
HINT:  To avoid a database shutdown, execute a full-database VACUUM in "debug".
WARNING:  database "debug" must be vacuumed within 999995 transactions
HINT:  To avoid a database shutdown, execute a full-database VACUUM in "debug".
WARNING:  database "debug" must be vacuumed within 999994 transactions
HINT:  To avoid a database shutdown, execute a full-database VACUUM in "debug".
WARNING:  database "debug" must be vacuumed within 999993 transactions
HINT:  To avoid a database shutdown, execute a full-database VACUUM in "debug".
WARNING:  database "debug" must be vacuumed within 999992 transactions
HINT:  To avoid a database shutdown, execute a full-database VACUUM in "debug".
WARNING:  database "debug" must be vacuumed within 999991 transactions
HINT:  To avoid a database shutdown, execute a full-database VACUUM in "debug".
WARNING:  database "debug" must be vacuumed within 999990 transactions
HINT:  To avoid a database shutdown, execute a full-database VACUUM in "debug".
WARNING:  database "debug" must be vacuumed within 999989 transactions
HINT:  To avoid a database shutdown, execute a full-database VACUUM in "debug".
WARNING:  database "debug" must be vacuumed within 999988 transactions
HINT:  To avoid a database shutdown, execute a full-database VACUUM in "debug".
WARNING:  database "debug" must be vacuumed within 999987 transactions
HINT:  To avoid a database shutdown, execute a full-database VACUUM in "debug".
WARNING:  database "debug" must be vacuumed within 999986 transactions
HINT:  To avoid a database shutdown, execute a full-database VACUUM in "debug".
WARNING:  database "debug" must be vacuumed within 999985 transactions
HINT:  To avoid a database shutdown, execute a full-database VACUUM in "debug".
WARNING:  database "debug" must be vacuumed within 999984 transactions
HINT:  To avoid a database shutdown, execute a full-database VACUUM in "debug".
WARNING:  database "debug" must be vacuumed within 999983 transactions
HINT:  To avoid a database shutdown, execute a full-database VACUUM in "debug".
ERROR:  could not access status of transaction 449971277
DETAIL:  could not open file "pg_clog/01AD": No such file or directory


Now what?

Thanks in advance.

Shailesh Singh

В списке pgsql-hackers по дате отправления:

Предыдущее
От: "Tomas Vondra"
Дата:
Сообщение: Re: Re: custom hash-based COUNT(DISTINCT) aggregate - unexpectedly high memory consumption
Следующее
От: Haribabu kommi
Дата:
Сообщение: Re: Compression of full-page-writes