Adds support for using pg_activity with Amazon RDS #45
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Taken from the following blog post and fork: http://blog.geesu.net/2015/06/09/using-pg_activity-with-amazon-rds/ https://github.com/Geesu/pg_activity/tree/feature/amazon-rds Just adds this as an commandline option instead of forcing it on all users. Should maintain backwards compatibility with the previous functionaility, just allows this to be used without errors when running against a remote RDS database.
|
👍 |
julmon
added a commit
that referenced
this pull request
Oct 17, 2015
Adds support for using pg_activity with Amazon RDS
|
Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Taken from the following blog post and fork:
http://blog.geesu.net/2015/06/09/using-pg_activity-with-amazon-rds/
https://github.com/Geesu/pg_activity/tree/feature/amazon-rds
Just adds this as an command line option instead of forcing it on all users. Should maintain backwards compatibility with the previous functionality, just allows this to be used without errors when running against a remote RDS database. All credit should go to @Geesu as he was the person that did the original legwork.
I can add documentation if you want, but I kept it minimal for now incase you would prefer a different approach to solving this problem.