Re: streaming header too small

From: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
To: Selena Deckelmann <selena(at)chesnok(dot)com>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Jaime Casanova <jaime(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: streaming header too small
Date: 2013-02-20 16:02:05
Message-ID: 5124F37D.9020303@vmware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 20.02.2013 17:53, Selena Deckelmann wrote:
> On Wed, Feb 20, 2013 at 6:23 AM, Magnus Hagander<magnus(at)hagander(dot)net>wrote:
>
>> Selena, was this reasonably reproducible for you? Would it be possible to
>> get a network trace of it to show of that's the kind of package coming
>> across, or by hacking up pg_basebackup to print the exact position it was
>> at when the problem occurred?
>
> This is happening with a very busy 700 GB system, so I'm going to rule out
> a network trace out for the moment. The error is occurring "sometime" in
> the middle of the backup. Last time it was at least 30-40 minutes into a 2
> hr backup.

If you could pinpoint the WAL position where the error happens, that
would already help somewhat. For starters, put pg_receivexlog to verbose
mode, so that it will print a line after each WAL segment. If my theory
is correct, the error should happen at xlogid boundaries, ie. just after
finishing a WAL segment whose filename ends with "FE".

- Heikki

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2013-02-20 16:20:41 Re: Materialized views WIP patch
Previous Message Magnus Hagander 2013-02-20 15:55:22 Re: streaming header too small