Prev: Bug on pg_lesslog
Next: pgsql: Make standby server continuouslyretry restoring the next WAL
From: Garick Hamlin on 11 Feb 2010 14:45
On Thu, Feb 11, 2010 at 01:22:44PM -0500, Kevin Grittner wrote:
> Heikki Linnakangas <heikki.linnakangas(a)enterprisedb.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(a)postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers

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

 | 
Pages: 1
Prev: Bug on pg_lesslog
Next: pgsql: Make standby server continuouslyretry restoring the next WAL