#14702 followup

From: dennis(dot)noordsij(at)alumni(dot)helsinki(dot)fi
To: pgsql-bugs(at)postgresql(dot)org
Subject: #14702 followup
Date: 2017-12-11 22:28:59
Message-ID: 56f0343e-43a2-a5bb-272e-5a8f68ca201d@iletsel.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

Using pg_waldump on the slave:

.... lots ....
rmgr: Transaction len (rec/tot):     34/    34, tx:    4886725, lsn:
9/988F3F08, prev 9/988F3EE0, desc: COMMIT 2017-12-06 22:32:25.326402 CET
rmgr: Transaction len (rec/tot):     34/    34, tx:    4886726, lsn:
9/988F3F30, prev 9/988F3F08, desc: COMMIT 2017-12-06 22:32:25.336578 CET
rmgr: Transaction len (rec/tot):     34/    34, tx:    4886722, lsn:
9/988F3F58, prev 9/988F3F30, desc: ABORT 2017-12-06 22:32:25.349521 CET
rmgr: XLOG        len (rec/tot):    106/   106, tx:          0, lsn:
9/988F3F80, prev 9/988F3F58, desc: CHECKPOINT_SHUTDOWN redo 9/988F3F80;
tli 1; prev tli 1; fpw true; xid 0:4886727; oid 2067430; multi 3972;
offset 11826; oldest xid 548 in DB 1; oldest multi 1 in DB 1;
oldest/newest commit timestamp xid: 0/0; oldest running xid 0; shutdown
pg_waldump: FATAL:  error in WAL record at 9/988F3F80: unexpected
pageaddr 9/938F4000 in log segment 000000000000000900000098, offset 9388032

using pg_waldump on the other segments that made it over:
    pg_waldump: FATAL:  could not find a valid record after 9/99000000

Using pg_waldump on the master:

.... lots ....
rmgr: Transaction len (rec/tot):     34/    34, tx:    4886725, lsn:
9/988F3F08, prev 9/988F3EE0, desc: COMMIT 2017-12-06 22:32:25.326402 CET
rmgr: Transaction len (rec/tot):     34/    34, tx:    4886726, lsn:
9/988F3F30, prev 9/988F3F08, desc: COMMIT 2017-12-06 22:32:25.336578 CET
rmgr: Transaction len (rec/tot):     34/    34, tx:    4886722, lsn:
9/988F3F58, prev 9/988F3F30, desc: ABORT 2017-12-06 22:32:25.349521 CET
rmgr: XLOG        len (rec/tot):    106/   106, tx:          0, lsn:
9/988F3F80, prev 9/988F3F58, desc: CHECKPOINT_SHUTDOWN redo 9/988F3F80;
tli 1; prev tli 1; fpw true; xid 0:4886727; oid 2067430; multi 3972;
offset 11826; oldest xid 548 in DB 1; oldest multi 1 in DB 1;
oldest/newest commit timestamp xid: 0/0; oldest running xid 0; shutdown
rmgr: Transaction len (rec/tot):     34/    34, tx:    4886727, lsn:
9/988F3FF0, prev 9/988F3F80, desc: COMMIT 2017-12-06 22:32:25.858243 CET
rmgr: Transaction len (rec/tot):     34/    34, tx:    4886728, lsn:
9/988F4030, prev 9/988F3FF0, desc: COMMIT 2017-12-06 22:32:26.213262 CET
rmgr: Transaction len (rec/tot):     34/    34, tx:    4886729, lsn:
9/988F4058, prev 9/988F4030, desc: COMMIT 2017-12-06 22:32:26.227834 CET
.... lots more ....

Please let me know if there is more I can check.

Best regards,
Dennis

Browse pgsql-bugs by date

  From Date Subject
Next Message Devrim Gündüz 2017-12-11 23:47:53 Re: BUG #14961: 9.6.6-4PGDG.rhel6.x86_64 introduces hanging init script
Previous Message dennis.noordsij 2017-12-11 22:15:27 BUG #14966: Related to #14702 / corruption in replication