| From: | Mariel Cherkassky <mariel(dot)cherkassky(at)gmail(dot)com> |
|---|---|
| To: | Kenneth Marshall <ktm(at)rice(dot)edu> |
| Cc: | Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: wal exist in slave but getting err requested WAL segment has already been removed |
| Date: | 2018-07-11 14:12:50 |
| Message-ID: | CA+t6e1nukx9YfKBiXn8y-G30Z0nRvaY_H4T2=Lda+Huxxu7tKg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
How can I get more info regarding this bug ? I would like to be sure that i
faced a real bug.
2018-07-11 16:50 GMT+03:00 Kenneth Marshall <ktm(at)rice(dot)edu>:
> On Wed, Jul 11, 2018 at 04:44:24PM +0300, Mariel Cherkassky wrote:
> > Yes i can see its content. However in the end of its content I'm getting
> > the next msg :
> > pg_xlogdump: FATAL: error in WAL record at 2E61/BDF59950: invalid magic
> > number 0000 in log segment 0000000000002E61000000BD, offset 16105472
> > Maybe this is the reason behind it ?
> >
>
> Hi Mariel,
>
> I do not know if this applies to your case, but 9.6.9 has this
> in the release notes:
>
> Fix a corner case where a streaming standby gets stuck at a WAL
> continuation record (Kyotaro Horiguchi)
>
> Regards,
> Ken
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mario De Frutos Dieguez | 2018-07-11 14:16:43 | row is too big: size 8168, maximum size 8160 |
| Previous Message | Kenneth Marshall | 2018-07-11 13:50:53 | Re: wal exist in slave but getting err requested WAL segment has already been removed |