chadbailey59

  • Joined on
chadbailey59 commented on pull request heroku/heroku#1605
@chadbailey59

I'm fine with that. For clarity's sake, the new output would look like: $ heroku pg:info === DATABASE, HEROKU_POSTGRESQL_CYAN Addon: glistening-gol…

chadbailey59 commented on pull request heroku/heroku#1605
@chadbailey59

@neovintage @bjeanes any thoughts? I know my most recent suggestion will cause a bit of a stir, but I think it helps Bo's message about addons and …

chadbailey59 commented on pull request heroku/heroku#1605
@chadbailey59

@neovintage I think the header goes away, and it's just multiple of these: Add-on: glistening-goldly-8123 Attachments: HEROKU_POSTGRESQL_CYAN, DATA…

chadbailey59 commented on pull request heroku/heroku#1605
@chadbailey59

Bo, thanks for laying all this out. I'm happy to be told so clearly how wrong my understanding is! :) I suspect I'm not the only person that still …

chadbailey59 commented on pull request heroku/heroku#1605
@chadbailey59

We're flirting with a larger conversation here. :) As far as I'm aware, Heroku Postgres is still the only addon (right now) in widespread use that …

chadbailey59 commented on pull request heroku/heroku#1605
@chadbailey59

I see what you're saying, Bo. And with all the new attachment stuff, it would make sense to solve this generically, as I've just made it worse on m…

chadbailey59 opened pull request heroku/heroku#1605
@chadbailey59
Identifying the cause of duplicate entries in `pg:info`
1 commit with 14 additions and 1 deletion
@chadbailey59

How do you feel about This command will remove all data from #{target.name} on #{app} and replace it with the contents of #{source.name}. to be ext…

@chadbailey59
Possible issue with leaving open database connections
@chadbailey59
chadbailey59 commented on pull request heroku/heroku#1539
@chadbailey59

I agree we should require an argument. :)

chadbailey59 commented on pull request heroku/heroku#1513
@chadbailey59

I just pushed a commit limiting to the last 10 operations each. It'll show 10 most recent restores and 10 most recent pg:copy operations. As far as…

@chadbailey59
chadbailey59 commented on pull request heroku/heroku#1513
@chadbailey59

I removed the ruby-version file. I also limited the restore and copy outputs to the 20 most recent. I absolutely think @neovintage 's concern about…

@chadbailey59
@chadbailey59
  • @chadbailey59 01cea92
    removed refs to app logs in transfer error output
chadbailey59 commented on pull request heroku/heroku#1513
@chadbailey59

Also, two bug fixes: Restores that came from htcat wouldn't show in restores. If an app had no backups but did have restores/copies, they wouldn't…

@chadbailey59
@chadbailey59
  • @chadbailey59 0efb830
    refactored pg:backups info tests inside pg:backups tests
chadbailey59 opened pull request heroku/heroku#1513
@chadbailey59
Additional output for `pg:backups` commands
2 commits with 110 additions and 0 deletions
@chadbailey59

Got it. I had sort-of figured that out yesterday, but was hoping I wouldn't have to log in each time. That seriously hampers the usability for me. :(

@chadbailey59
pg:backups is prefixing manual backups with "a"
@chadbailey59

Having the same problem. @brschwar , did you do anything special to get it to work?

@chadbailey59

What if we left the default behavior as-is, but had a simple DSL to override it in an initializer? If you don’t do anything, it will raise an Excep…

@chadbailey59

What if we left the default behavior as-is, but had a simple DSL to override it in an initializer? If you don’t do anything, it will raise an Excep…

@chadbailey59

I can definitely see arguments from both sides—since rack-timeout kind of exists outside the context of an entire Rails app, you wouldn't want Rail…

@chadbailey59
pg:maintenance window setting is confusing
chadbailey59 commented on pull request heroku/heroku#1495
@chadbailey59

@uhoh-itsmaciek , I changed it to quiet. (I didn't like suppress anyway.) @will re: our discussion in HipChat: I agree this isn't necessary because…