Re: SR fails to send existing WAL file after off-line copy

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Greg Smith <greg(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Matt Chesler <matt(at)pragmatrading(dot)com>
Subject: Re: SR fails to send existing WAL file after off-line copy
Date: 2010-11-01 06:28:32
Message-ID: 4CCE5E10.7060403@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 01.11.2010 05:21, Robert Haas wrote:
> There seem to be two cases in the code that can generate that error.
> One, attempting to open the file returns ENOENT. Two, after the data
> has been read, the last-removed position returned by
> XLogGetLastRemoved precedes the data we think we just read, implying
> that it was overwritten while we were in the process of reading it.
> Does your installation have debugging symbols? Can you figure out
> which case is triggering (inside XLogRead) and what the values of log,
> seg, lastRemovedLog, and lastRemovedSeg are?

An easy way to find out which ereport() it is is to "set
log_error_verbosity='verbose'" and re-run the test. You then get the
file and line number of the ereport in the log.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2010-11-01 07:37:05 Re: SR fails to send existing WAL file after off-line copy
Previous Message Tom Lane 2010-11-01 05:12:29 Re: Maximum function call nesting depth for regression tests