Quoting Tom Lane <tgl@sss.pgh.pa.us>:
> Network Administrator <netadmin@vcsn.com> writes:
> > ..if I using the psql client, and issue a "select * from <corrupt table
> name>
> > limit 5" if get this...
>
> > PANIC: read of clog file 5, offset 16384 failed: Success
>
> Hm, not good :-(. What files actually exist in $PGDATA/pg_clog/ (names
> and sizes)?
Here you go...
-rw------- 1 postgres users 262144 Jul 20 15:53 0000
-rw------- 1 postgres users 262144 Jul 31 12:57 0001
-rw------- 1 postgres users 262144 Aug 12 17:32 0002
-rw------- 1 postgres users 262144 Aug 26 00:15 0003
-rw------- 1 postgres users 262144 Sep 9 23:44 0004
-rw------- 1 postgres users 16384 Sep 10 21:21 0005
> > So back to my original question. What are the recover procedures (if
> > any) that should be tried before I grab my PGDATA path from tape?
>
> You may be up against having to do that, but some investigation first
> seems called for.
Yep, its ready to go. When and if nothing surgical can be done.
> regards, tom lane
>
--
Keith C. Perry
Director of Networks & Applications
VCSN, Inc.
http://vcsn.com
____________________________________
This email account is being host by:
VCSN, Inc : http://vcsn.com
