On 11/14/2012 03:32 PM, Martin Rode wrote:
The point is, you can do incremental backups easily if you store
attachments in files. If you store them inside the database a full dump
gets huge and can take a lot of time.
Yes. An artifact of pg_dump (and dumpall). IMO PITR backups are a better
solution than moving parts of the db where pg_dump cannot see them. But
there are drawbacks to PITR too, and I see your point.
(Abhijit showed me a newly submitted patch for pg_dump which goes some
way towards resolving this.)
You can shrink the backups by deleting attachments (conditionally,
blah), or by not backing up the entire db.
Why would you not want to backup the entire db?
Beats me. I've seen several people do it. Shocking.
Arnt
