In case this is happening to anyone else - here's a workaround to at least be able to give yourself an estimate...
Go to heroku console - find the number of records in the table Class.count Switch db's in your psql client and select count(*), Now() in the table to see how fast it's updating. Do it again a few minutes later and extrapolate your finish time. The table I am looking at is importing ~9K rows/minute. On Oct 15, 2010, at 12:06 PM, Mark Swardstrom wrote: > When I pull from heroku I don't see the ETA update, it just updates when the > row is filled in completely. > > $ heroku db:pull --app production > > Loaded Taps v0.3.13 > Auto-detected local database: > postgres://localhost/myapp_development?encoding=utf8 > Warning: Data in the database > 'postgres://localhost/myapp_development?encoding=utf8' will be overwritten > and will not be recoverable. > Are you sure you wish to continue? (y/n)? y > > On "receiving tables" - the row shows ETA: 00:00:00 until it switches to > Time: 00:05:42 (for example) > > I have some tables that are large and keep timing out for one reason or > another, it would be great to know how long I need to go so I can make sure > network disruptions / work distractions are avoided for an extended period of > time. > > This used to work, but it hasn't been lately... > > - Mark > -- 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.
