On Fri, Feb 15, 2013 at 10:57 AM, Maciek Sakrejda <maciek@heroku.com> wrote=
:
> On Fri, Feb 15, 2013 at 7:10 AM, Heikki Linnakangas <
> hlinnakangas@vmware.com> wrote:
>
>> Hmm, that sure looks like the same issue Kyotaro HORIGUCHI reported (
>> http://www.postgresql.org/message-id/20121206.130458.170549097.horiguchi=
.kyotaro@lab.ntt.co.jp),
>> but that was fixed in 9.1.8. Maybe there's some corner case where it's
>> still not working.
>>
>
> We reproduce it on a separate replica with the same base backup. Tried a
> new base backup; that worked.
>
>
>> Did you keep a copy of the WAL involved? Any chance of running xlogdump
>> on it, and posting the results, or just sending over the WAL files so I
>> could take a look?
>>
>
> Yes, we have the WAL. I can't share it as it's customer data. I tried
> setting up xlogdump (this, yes? https://github.com/snaga/xlogdump ), but
> ran into problems building it (tag REL0_5_2):
>
> root@host:/home/heroku/xlogdump# PATH=3D/usr/lib/postgresql/9.1/bin:$PATH
> USE_PGXS=3D1 make
> gcc -g -O2 -fstack-protector --param=3Dssp-buffer-size=3D4 -Wformat
> -Wformat-security -Werror=3Dformat-security -fPIC -Wall -Wmissing-prototy=
pes
> -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels
> -Wformat-security -fno-strict-aliasing -fwrapv -fexcess-precision=3Dstand=
ard
> -g -I/usr/include/postgresql -DDATADIR=3D\"/usr/share/postgresql/9.1\" -I=
.
> -I. -I/usr/include/postgresql/9.1/server -I/usr/include/postgresql/intern=
al
> -D_FORTIFY_SOURCE=3D2 -DLINUX_OOM_ADJ=3D0 -D_GNU_SOURCE -I/usr/include/li=
bxml2
> -I/usr/include/tcl8.5 -c -o xlogdump.o xlogdump.c
> xlogdump.c: In function =91ReadRecord=92:
> xlogdump.c:321:7: warning: format =91%u=92 expects argument of type =91un=
signed
> int=92, but argument 3 has type =91long unsigned int=92 [-Wformat]
> xlogdump.c: At top level:
> xlogdump.c:865:1: error: conflicting types for =91ExceptionalCondition=92
> /usr/include/postgresql/postgres.h:686:13: note: previous declaration of
> =91ExceptionalCondition=92 was here
> make: *** [xlogdump.o] Error 1
>
>
Can you try master on xlogdump instead of the release? I have fixed a few
bugs there a year ago that don't seem to be in the release, and will fix
more if necessary.
--=20
fdr
