On 10/8/13 5:55 AM, shailesh singh wrote:
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
Unless I'm mistaken, that missing CLOG file is
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 99 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in
debug.
ERROR:
*Don't* VACUUM FULL. Just VACUUM. It's not the same thing.
...Robert
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On 19/04/12 06:23, Josh Berkus wrote:
Nagaraj,
i am nagaraj, i am newbi in this database world. i required your help.
2 dyas back i formatted one of my client system. which is having postgresql
8.2 database that was having data. but i am not taken backup of the data.
1) how to take the data
Hi team,
i am nagaraj, i am newbi in this database world. i required your help.
2 dyas back i formatted one of my client system. which is having postgresql
8.2 database that was having data. but i am not taken backup of the data.
1) how to take the data from the formatted harddisk. ?
2) how many
Nagaraj,
i am nagaraj, i am newbi in this database world. i required your help.
2 dyas back i formatted one of my client system. which is having postgresql
8.2 database that was having data. but i am not taken backup of the data.
1) how to take the data from the formatted harddisk. ?
2) how
