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

Re: Differential backup

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Simon Riggs" <simon(at)2ndQuadrant(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Differential backup
Date: 2010-04-27 13:59:03
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Simon Riggs <simon(at)2ndQuadrant(dot)com> wrote:
> Thinking about allowing a backup to tell which files have changed
> in the database since last backup. This would allow an external
> utility to copy away only changed files.
> Now there's a few ways of doing this and many will say this is
> already possible using file access times.
Who would say otherwise?  Under what circumstances would PostgreSQL
modify a file without changing the "last modified" timestamp or the
file size?  If you're concerned about the converse, with daemon-
based rsync you can copy just the modified portions of a file on
which the directory information has changed.  Or is this targeting
platforms which don't have rsync?
> An explicit mechanism where Postgres could authoritatively say
> which files have changed would make many feel safer, especially
> when other databases also do this.
Why?  I must be missing something, because my feeling is that if you
can't trust your OS to cover something like this, how can you trust
any application *running* under that OS to do it?
> Is this route worthwhile?
I'm not seeing it, but I could be missing something.  Can you
describe a use case where this would be beneficial?

In response to


pgsql-hackers by date

Next:From: Simon RiggsDate: 2010-04-27 14:08:11
Subject: Re: Differential backup
Previous:From: Simon RiggsDate: 2010-04-27 13:55:30
Subject: Re: Differential backup

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