FYI, I asked Heroku support these same questions. Bundles:capture uses pg_dump to generate the database dump, and should give a consistent dump.
db:push and db:pull may give inconsistent data if used on a running application, so always put it in maintenance mode first. On Mar 23, 12:26 pm, Jesse <[email protected]> wrote: > I don't know the answers to your questions > > but after an app is up and running (in production) I don't think you > would ever want to call db:push? > as it would be pushing data (and more) from your development database > to production; > I think it is meant as a starting point to initially launch your > application (at least that is how I used it) - after that i would use > migrations to incrementally add app specific data and schema changes > > however for my staging site I will often pull down the production > data; restore that over my development db and then use heroku db:reset > and heroku db:push on the staging site to DELETE and overwrite my > staging db on heroku and test against that. > > fromhttp://docs.heroku.com/taps#import-push-to-heroku > "This pushes the contents (schema, data, indexes, sequences) of > whatever database is specified in config/database.yml to Heroku." (the > config/database.yml on your local machine) > > On Mar 22, 8:57 pm, Mike <[email protected]> wrote: > > > What happens if my application is active while I either call > > bundles:capture or db:push or db:pull? > > > In the case of bundles:capture or db:pull, is it possible for me to > > get an internally inconsistent dump from the database if changes are > > made to multiple tables of the database while they are in process, and > > some of these tables have already been processed and others have not? > > > What about with db:push? Is it possible for the user to see the app in > > an internally inconsistent state, where some tables have been pushed > > up, but others have not yet been? Worse yet, if the user does > > something that changes the state of some tables, is it possible this > > will result in an internally consistent state, for example, where the > > user adds something to a table that causes a primary key conflict with > > something being pushed up? > > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
