| From: | Mike Broers <mbroers(at)gmail(dot)com> |
|---|---|
| To: | andres(at)anarazel(dot)de |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: root cause of corruption in hot standby |
| Date: | 2018-10-10 19:29:44 |
| Message-ID: | CAB9893gk+xUQrvhn7NnE7EukjtBn9+whkeQF2uoivBnobCM5eg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
No I havent. Not sure how to or what it would reveal but willing to give
it a try.
On Wed, Oct 10, 2018 at 2:25 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> Hi,
>
> On 2018-09-06 12:28:18 -0500, Mike Broers wrote:
> > So I have discovered corruption in a postgres 9.5.12 read replica, yay
> > checksums!
> >
> > 2018-09-06 12:00:53 CDT [1563]: [4-1] user=postgres,db=production
> WARNING:
> > page verification failed, calculated checksum 3482 but expected 32232
> >
> > 2018-09-06 12:00:53 CDT [1563]: [5-1] user=postgres,db=production ERROR:
> > invalid page in block 15962 of relation base/16384/464832386
>
> Have you compared whether that block looks significantly different on
> the primary from the standby with a hex editor?
>
> Greetings,
>
> Andres Freund
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mariel Cherkassky | 2018-10-11 06:56:48 | does work_mem is used on temp tables? |
| Previous Message | Andres Freund | 2018-10-10 19:25:53 | Re: root cause of corruption in hot standby |