Re: Updated backup APIs for non-exclusive backups - Mailing list pgsql-hackers

From Laurenz Albe
Subject Re: Updated backup APIs for non-exclusive backups
Date
Msg-id 79ea3257ccba07bd52a46fa687434c0b39f6025b.camel@cybertec.at
Whole thread Raw
In response to Re: Updated backup APIs for non-exclusive backups  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Updated backup APIs for non-exclusive backups  (David Steele <david@pgmasters.net>)
List pgsql-hackers
On Mon, 2018-11-26 at 10:18 +0100, Magnus Hagander wrote:
> > [about managing backups from pre- and post-file-system-backup scrips]
> > > I agree with your point that it's not an uncommon thing to need. If a good solution
> > > for it can be proposed that requires the exclusive backup interface, then I wouldn't
> > > be against un-deprecating that.  But that's going to require a lot more than just a
> > > documentation change, IMHO. What could perhaps be handled with a documentation change,
> > > however, is to document a good way for this type of setup to use the new interfaces.
> > 
> > Good point, and it puts the ball in my court :^)
> 
> Enjoy :)

I have come up with some sample code here:
https://github.com/cybertec-postgresql/safe-backup

This just uses bash and psql.
Does that look reasonably safe?

It's probably too big to be introduced into the documentation, but maybe
we could add it to the Wiki.

Yours,
Laurenz Albe



pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: Connections hang indefinitely while taking a gin index's LWLockbuffer_content lock
Next
From: Andres Freund
Date:
Subject: Re: automatically assigning catalog toast oids