Skip to content
This repository has been archived by the owner on Feb 12, 2022. It is now read-only.

Show backups that will be migrated from PGBackups #1490

Merged
merged 4 commits into from
Apr 8, 2015

Conversation

msakrejda
Copy link
Contributor

This cleans things up a bit and adds support for displaying backups from the old PGBackups system after we migrate them.

/cc @neovintage (N.B.: the backup naming scheme here is one suggested by pvh: just prefix anything coming from PGBackups with o--I can easily change this to something else that follows the same general mechanism)

@neovintage
Copy link
Contributor

+1

On Tue, Apr 7, 2015 at 11:40 PM, Maciek Sakrejda notifications@github.com
wrote:

This cleans things up a bit and adds support for displaying backups from
the old PGBackups system after we migrate them.

/cc @neovintage https://github.com/neovintage (N.B.: the backup naming
scheme here is one suggested by pvh: just prefix anything coming from
PGBackups with o--I can easily change this to something else that follows

the same general mechanism)

You can view, comment on, or merge this pull request online at:

#1490
Commit Summary

  • Show old pgbackups transfer names
  • Better transfer_name function; use it more consistently
  • Cleaner support for PGBackups backups

File Changes

Patch Links:


Reply to this email directly or view it on GitHub
#1490.

@hgmnz
Copy link
Contributor

hgmnz commented Apr 8, 2015

Oh yes, +1!

jdx pushed a commit that referenced this pull request Apr 8, 2015
…backups

Show backups that will be migrated from PGBackups
@jdx jdx merged commit 698e953 into heroku:master Apr 8, 2015
@msakrejda
Copy link
Contributor Author

Thanks!

@hgmnz
Copy link
Contributor

hgmnz commented Apr 8, 2015

woot, thanks @dickeyxxx

@neovintage
Copy link
Contributor

thanks @dickeyxxx !

On Wed, Apr 8, 2015 at 4:41 PM, Harold Giménez notifications@github.com
wrote:

woot, thanks @dickeyxxx https://github.com/dickeyxxx


Reply to this email directly or view it on GitHub
#1490 (comment).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants