| From: | Chris Travers <chris(dot)travers(at)gmail(dot)com> |
|---|---|
| To: | Vladimir Borodin <root(at)simply(dot)name> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Funny WAL corruption issue |
| Date: | 2017-08-10 12:39:22 |
| Message-ID: | CAKt_ZfvVhv=rUHanjy_x1MOoSs53kTGmgvJPJijrD+24-zEdaA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Yes. Exactly the same output until a certain point where pg_xlogdump dies
> with an error. That is the same LSN where PostgreSQL died with an error on
> restart.
>
One other thing that is possibly relevant after reading through the last
bug report is the error pgxlogdumo gives:
pg_xlogdump: FATAL: error in WAL record at 1E39C/E1117FB8: unexpected
pageaddr 1E375/61118000 in log segment 000000000001E39C000000E1, offset
1146880
> --
Best Wishes,
Chris Travers
Efficito: Hosted Accounting and ERP. Robust and Flexible. No vendor
lock-in.
http://www.efficito.com/learn_more
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksander Alekseev | 2017-08-10 12:48:14 | Re: Funny WAL corruption issue |
| Previous Message | Sokolov Yura | 2017-08-10 12:30:25 | Re: Lazy hash table for XidInMVCCSnapshot (helps Zipfian a bit) |