Skip site navigation (1) Skip section navigation (2)

Re: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL

From: Garick Hamlin <ghamlin(at)isc(dot)upenn(dot)edu>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Aidan Van Dyk<aidan(at)highrise(dot)ca>, Simon Riggs <simon(at)2ndQuadrant(dot)com>, Fujii Masao<masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development<pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL
Date: 2010-02-11 19:45:13
Message-ID: 20100211194513.GC5500@isc.upenn.edu (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-docspgsql-hackers
On Thu, Feb 11, 2010 at 01:22:44PM -0500, Kevin Grittner wrote:
> Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
>  
> > I think 'rsync' has the same problem.
>  
> There is a switch you can use to create the problem under rsync, but
> by default rsync copies to a temporary file name and moves the
> completed file to the target name.
>  
> -Kevin

I don't use PITR, So I don't know any of the well understood facts about 
PITR with postgres, but my understanding with rsync is ...

It doesn't fsync data before rename, its something like: open / write / 
close / rename, which could lead to zero length files on some filesystems.  
(are there other anomalies to worry about here?)

Would that be a concern?  

Garick

> 
> -- 
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers

In response to

pgsql-docs by date

Next:From: Fujii MasaoDate: 2010-02-12 01:57:53
Subject: Re: Confusing link in streaming replication section
Previous:From: Kevin GrittnerDate: 2010-02-11 18:22:44
Subject: Re: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2010-02-11 19:46:37
Subject: Re: Re: [COMMITTERS] pgsql: Remove old-style VACUUM FULL (which was known for a little while
Previous:From: Robert HaasDate: 2010-02-11 19:42:49
Subject: Re: [PATCH] Provide rowcount for utility SELECTs

pgsql-committers by date

Next:From: Alvaro HerreraDate: 2010-02-11 19:46:37
Subject: Re: Re: [COMMITTERS] pgsql: Remove old-style VACUUM FULL (which was known for a little while
Previous:From: Robert HaasDate: 2010-02-11 19:36:37
Subject: Re: Re: [COMMITTERS] pgsql: Remove old-style VACUUM FULL (which was known for a little while

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group