Feature/loggging of schema changes#92
Merged
AlexanderMann merged 6 commits intodatamill-co:masterfrom Jan 28, 2019
Merged
Conversation
83e34dd to
a7eeb46
Compare
awm33
approved these changes
Jan 27, 2019
Closed
This file contains hidden or 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
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.
Motivation
Issues posted by users of this codebase sometimes have a lack of usable logs present. Additionally, when testing, or debugging in production, more fine grained information can be quite useful.
Notes
This is all opt-in-enabled by setting the new config option:
logging_level, toDEBUGor lower.This pr adds special logging with durations for:
sql_base.upsert_table_helperEach decision which modifies the table in some manner is logged:
psycopg2.connection/psycopg2.cursorqueriesEvery query run will output logs similar to:
Suggested Musical Pairing
Windows creeking from the cold