> The only *error* I see is when you apparently manually kill the process.
You mean walreceiver process?? 'FATAL: terminating walreceiver process due
to administrator command' ?
Actually, I didn't kill the receiver. It is done by postgres itself, as far
as I understand.
I restart this node using
On 1/29/19 9:57 PM, Abdullah Al Maruf wrote:
Hi Michael
> This is pointing out to the end of WAL for the current timeline. You
> may face it after reading a WAL segment in an area which has been used
> in the past for a recycled segment.
Are you talking about error `LOG: invalid record length
Hi Michael
> This is pointing out to the end of WAL for the current timeline. You
> may face it after reading a WAL segment in an area which has been used
> in the past for a recycled segment.
Are you talking about error ` LOG: invalid record length at 0/B98:
wanted 24, got 0` ?
or,
`LOG:
On Tue, Jan 29, 2019 at 07:13:11PM +0600, Abdullah Al Maruf wrote:
> When I try to attach an old master with 'archiving set to on` as a new
> standby, `pg_rewind` doesn't throw any error, But, when the database
> starts, The following error appears:
>
> ```
> LOG: invalid record length at 0/B
