Re: Hot Backup with rsync fails at pg_clog if under load

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Linas Virbalas <linas(dot)virbalas(at)continuent(dot)com>, Euler Taveira de Oliveira <euler(at)timbira(dot)com>, Florian Pflug <fgp(at)phlo(dot)org>
Subject: Re: Hot Backup with rsync fails at pg_clog if under load
Date: 2011-09-23 16:03:13
Message-ID: CABUevEzH3q=q8XMZ+murfoyE=pvWko6UqO9t8JkfqVNJ2QpVjg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sep 23, 2011 5:59 PM, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>
wrote:
>
>
> Excerpts from Linas Virbalas's message of vie sep 23 09:47:20 -0300 2011:
> > On 9/23/11 12:05 PM, "Heikki Linnakangas"
> > <heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
>
> > But on the standby its size is the old one (thus, it seems, that the
size
> > changed after the rsync transfer and before the pg_stop_backup() was
> > called):
> >
> > ls -l pg_clog/
> > total 8
> > -rw------- 1 postgres postgres 8192 Sep 23 14:31 0000
>
> Sounds like rsync is caching the file size at the start of the run, and
> then copying that many bytes, ignoring the growth that occurred after it
> started.
>

That pretty much matches what Daniel does when he got the same failure case.

Is this not allowed? Shouldn't wal replay fix this?

/Magnus

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2011-09-23 16:10:39 Re: Hot Backup with rsync fails at pg_clog if under load
Previous Message Alvaro Herrera 2011-09-23 15:58:59 Re: Hot Backup with rsync fails at pg_clog if under load