From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Aidan Van Dyk <aidan(at)highrise(dot)ca> |
Cc: | Florian Pflug <fgp(at)phlo(dot)org>, Daniel Farina <daniel(at)heroku(dot)com>, Chris Redekop <chris(at)replicon(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Hot Backup with rsync fails at pg_clog if under load |
Date: | 2011-10-26 13:12:27 |
Message-ID: | CA+U5nML+fJgz-NdZrGX+R3m6JKnT1JC=v0iXkkSAsojnsqqPoQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Oct 26, 2011 at 12:54 PM, Aidan Van Dyk <aidan(at)highrise(dot)ca> wrote:
> The read fails because their is no data at the location it's trying to
> read from, because clog hasn't been extended yet by recovery.
You don't actually know that, though I agree it seems a reasonable
guess and was my first thought also.
The error is very specifically referring to 22811359, which is the
nextxid from pg_control and updated by checkpoint.
22811359 is mid-way through a clog page, so prior xids will already
have been allocated, pages extended and then those pages fsyncd before
the end of pg_start_backup(). So it shouldn't be possible for that
page to be absent from the base backup, unless the base backup was
taken without a preceding checkpoint, which seems is not the case from
the script output.
Note that if you are correct, then the solution is to extend clog,
which Florian disagrees with as a solution.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2011-10-26 13:51:49 | Re: TOAST versus VACUUM, or "missing chunk number 0 for toast value" identified |
Previous Message | Aidan Van Dyk | 2011-10-26 11:54:16 | Re: Hot Backup with rsync fails at pg_clog if under load |