File tree 2 files changed +25
-1
lines changed
2 files changed +25
-1
lines changed Original file line number Diff line number Diff line change @@ -10,7 +10,7 @@ pairing with smart people at Hashrocket.
10
10
11
11
For a steady stream of TILs, [ sign up for my newsletter] ( https://crafty-builder-6996.ck.page/e169c61186 ) .
12
12
13
- _ 1187 TILs and counting..._
13
+ _ 1188 TILs and counting..._
14
14
15
15
---
16
16
@@ -339,6 +339,7 @@ _1187 TILs and counting..._
339
339
### Heroku
340
340
341
341
- [ Deploy A Review App To A Different Stack] ( heroku/deploy-a-review-app-to-a-different-stack.md )
342
+ - [ Diagnose Problems In A Heroku Postgres Database] ( heroku/diagnose-problems-in-a-heroku-postgres-database.md )
342
343
- [ Set And Show Heroku Env Variables] ( heroku/set-and-show-heroku-env-variables.md )
343
344
- [ SSH Into Heroku Server Hosting App] ( heroku/ssh-into-heroku-server-hosting-app.md )
344
345
Original file line number Diff line number Diff line change
1
+ # Diagnose Problems In A Heroku Postgres Database
2
+
3
+ Heroku keeps track of all kinds of diagnostics on the performance of your app's
4
+ database. From long running queries and transactions to index cache hit rates
5
+ to unused indexes to tables with bloat.
6
+
7
+ Running the ` pg:diagnose ` command for your Heroku app will surface all of these
8
+ details in the terminal.
9
+
10
+ ``` bash
11
+ $ heroku pg:diagnose -a APP_NAME
12
+ ```
13
+
14
+ The report will start with the biggest problem areas which it color codes in
15
+ red. If your app is experiencing degraded performance, the list of red items
16
+ would be a good place to start investigating.
17
+
18
+ The report will then list less urgent problem areas. Those will be color coded
19
+ yellow. Though Heroku has deemed these less serious, you may still want to deal
20
+ with these.
21
+
22
+ All the other areas of diagnose will fall into the _ green_ bucket. Meaning
23
+ Heroku doesn't see any issues in those areas.
You can’t perform that action at this time.
0 commit comments