You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow users to keep a memory of the latest "copy" of each particular repo / migration combination.
Every so often, we'll launch a background task at the start of pgsh to look at all the databases with the same migration history, md5sum the file representing the latest migration, and see if the current database has a newer write than a different version of the same database (not really fleshed out)
For each config.project_id, we'll keep the last n
project ID could be, by default, the name of the repo / package.json
Commands:
backup pause
backup on
backup off
backup 50G
backup 30
backup peek -- switch to the backup database
backup restore [target] -- clone the backup database into a new named database (or the current one if none given)
The text was updated successfully, but these errors were encountered:
sastraxi
added
question
Further information is requested
long term
Not going to be fixed for a while, but an ideal version of this project has this issue resolved.
labels
Dec 1, 2019
Allow users to keep a memory of the latest "copy" of each particular repo / migration combination.
Every so often, we'll launch a background task at the start of
pgsh
to look at all the databases with the same migration history, md5sum the file representing the latest migration, and see if the current database has a newer write than a different version of the same database (not really fleshed out)For each
config.project_id
, we'll keep the last npackage.json
Commands:
backup pause
backup on
backup off
backup 50G
backup 30
backup peek
-- switch to the backup databasebackup restore [target]
-- clone the backup database into a new named database (or the current one if none given)The text was updated successfully, but these errors were encountered: