Miguel wrote:
Tom Lane wrote:
Increasing the WAL start address might help (see the pg_resetxlog man
page). Realize that you're probably going to be dealing with corrupted
data, however :-(
regards, tom lane
Ops, foget the last email, i reread the man, this is what i have to do:
shiva2 pg_xlog # ls -l
total 180448
-rw------- 1 postgres postgres 16777216 Oct 28 18:05
00000001000000980000001A
-rw------- 1 postgres postgres 16777216 Oct 28 18:07
00000001000000980000001B
-rw------- 1 postgres postgres 16777216 Oct 28 18:10
00000001000000980000001C
-rw------- 1 postgres postgres 16777216 Oct 28 18:10
00000001000000980000001D
-rw------- 1 postgres postgres 16777216 Oct 28 17:25
00000001000000980000001E
-rw------- 1 postgres postgres 16777216 Oct 28 17:28
00000001000000980000001F
-rw------- 1 postgres postgres 16777216 Oct 28 17:37
000000010000009800000020
-rw------- 1 postgres postgres 16777216 Oct 28 17:51
000000010000009800000021
-rw------- 1 postgres postgres 16777216 Oct 28 17:53
000000010000009800000022
-rw------- 1 postgres postgres 16777216 Oct 28 17:46
000000010000009800000023
-rw------- 1 postgres postgres 16777216 Oct 28 17:49
000000010000009800000024
drwx------ 2 postgres postgres 4096 Apr 22 2005 archive_status
So :
pg_resetxlog -l 0x01, 0x98, 0x25 dir_data
Is this ok?
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
