| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ray Stell <stellr(at)cns(dot)vt(dot)edu> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: unexpected pageaddr |
| Date: | 2011-02-02 23:57:36 |
| Message-ID: | 5484.1296691056@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Ray Stell <stellr(at)cns(dot)vt(dot)edu> writes:
> On Wed, Feb 02, 2011 at 06:32:22PM -0500, Tom Lane wrote:
>> "unexpected pageaddr" is just one of the standard tests for detecting
>> end of WAL, so I don't think this is anything to be surprised about.
>> It looks to me like the standby applied all the WAL it had and then
>> connected to the master for more.
> thanks, Tom. I suppose it's the order that trips me up:
> starts at 65...
> reached a 66...
> unexpected at 62...
Well, the point of the "unexpected pageaddr" message is exactly that the
WAL location it found in the next file wasn't the expected next location
in sequence (which would have to be something larger than 0/66000000).
This indicates that the next file isn't really new WAL, but a segment
file that was recycled (by renaming it to a higher file number) but not
yet overwritten with new data.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adarsh Sharma | 2011-02-03 08:57:57 | Select Command in Procedures |
| Previous Message | French, Martin | 2011-02-02 23:55:42 | Re: unexpected pageaddr |