You can create the missing clog file as a file 256K big full of zeros. Then
dump, initdb and restore.
And upgrade the db to the latest minor version.
On Tue, Oct 21, 2003 at 04:49:26PM -0700, Adam Haberlach wrote:
We had one of our databases suddenly try to reference a pg_clog
file that didn't exist whenever we attempted to select from a certain
table. Anyone know of a way to recover from this? Is there a way to
reset the transaction logs and just use whatever data is actually
stored in the system?
--
Adam Haberlach | "We spent the 90's all trying to figure out
ad**@mediariffic.com | how to get email and the 00's trying to
http://mediariffic.com | figure out how to not get email."
| -- Joe Gross
---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings
--
Martijn van Oosterhout <kl*****@svana.org> http://svana.org/kleptog/ "All that is needed for the forces of evil to triumph is for enough good
men to do nothing." - Edmond Burke
"The penalty good people pay for not being interested in politics is to be
governed by people worse than themselves." - Plato
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see
http://www.gnupg.org
iD8DBQE/lei/Y5Twig3Ge+YRAgD/AKDBi7WsFUL3MiyeptvqW2B09e66QgCfanB7
4t6sRp1EdygSieJ0B3nOvyA=
=32eB
-----END PGP SIGNATURE-----