| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> | 
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org | 
| Subject: | Differential backup | 
| Date: | 2010-04-27 13:30:14 | 
| Message-ID: | 1272375014.4161.7260.camel@ebony | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
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.
An explicit mechanism where Postgres could authoritatively say which
files have changed would make many feel safer, especially when other
databases also do this.
We keep track of which files require fsync(), so we could also keep
track of changed files using that same information.
Is this route worthwhile? Or in some way unacceptable?
-- 
 Simon Riggs           www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2010-04-27 13:50:44 | Re: Differential backup | 
| Previous Message | Simon Riggs | 2010-04-27 13:20:53 | Re: recovery_connections cannot start |