"Matthew T. O'Connor" <matthew@zeut.net> writes:
>  Here is what I find in pg_xlog:
> [EMAIL PROTECTED] pg_xlog]# ls -l
> total 114840
> -rw-------   1 postgres postgres 16777216 Aug  7 18:29 
> 000000010000000200000016

So are you still getting the error?  This looks like your WAL is now
up to 2/16xxxxxx, so that sanity check shouldn't be noticing a problem
anymore.  Not that that should make us feel better --- there's
definitely something fishy here.

> I'm not sure how to get what you are looking for with pg_filedump, I've 
> got pg_filedump compiled, and tried pg_filedump-4.0/pg_filedump -f -R 
> 3421 ./9534098  but I don't really know how to read the output.

I didn't ask you if *you* knew what the output meant ;-) but it should
show the page LSN like this:

 LSN:  logid      0 recoff 0x00000020      Special  8192 (0x2000)
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

               http://archives.postgresql.org

Reply via email to