Re: Re: redo failed in physical streaming replication while stopping the master server

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: lannis <msp548546(at)163(dot)com>
Cc: PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: redo failed in physical streaming replication while stopping the master server
Date: 2016-03-03 11:19:18
Message-ID: CAB7nPqSyiMP0Er8Xw713YU7W-EmSVGWgnrhs5SMzt4=ovgGU=g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Mar 3, 2016 at 6:58 PM, lannis <msp548546(at)163(dot)com> wrote:
> So in the replay scenario, before we read the page from wal segment file,
> using the specical RecPtr which point to the next page header address, can
> we predicat the page header is a long or short?

I am not sure I am getting what you are looking for, but if you mean
if we can predict it or not, the answer is yes. A long header is used
at the beginning of a WAL segment, by default 16MB, and the short
header at the beginning of a WAL page, or XLOG_BLCKSZ, 8kB by default.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Mithun Cy 2016-03-03 11:20:17 Re: POC: Cache data in GetSnapshotData()
Previous Message Pavel Stehule 2016-03-03 11:15:13 Re: proposal: psql autocomplete for casting