On Wed, Mar 11, 2015 at 9:55 AM, Andrew Sullivan <a...@crankycanuck.ca> wrote:
> On Wed, Mar 11, 2015 at 09:40:09AM -0400, Joseph Kregloh wrote: > > Have you looked into Barman? http://www.pgbarman.org/ It does what you > > want. You can take a full daily backup and it keeps track of the WAL > files > > to allow for a PITR. > > I just had a look at the documentation (and the rest of your mail), > and this doesn't actually seem to do what the OP wanted, which is to > get PITR _per database_ in the same cluster. Upthread someone > suggested a way around this, which is to PITR a cluster to a > known-good point and then pg_dump the target database. This is where Barman comes in. It would take care of handling all of the stuff required for a PITR. Then he can do the pg_dump for a selected database. Barman does backup the entire cluster. > But if Barman > can do this automatically, that'd be cool (it's just not in the docs). > > Barman does look like a nice convenience package for managing > WAL-shipping type backup installations instead of building one's own > scripts, so this note isn't intended as a criticism of the package. > I'm just not sure it does the thing requested in this case. > > A > > -- > Andrew Sullivan > a...@crankycanuck.ca > > > -- > Sent via pgsql-general mailing list (pgsql-general@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general >
