Resolve SQL Lock Issues in df_to_psql
Function
#38
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.
I encountered issues with SQL locks (observed in pgAdmin) that were preventing the model from completing its run. The locks were occurring specifically in the
df_to_psql
function withininput_data_functions.py
. After reviewing the SQLAlchemy documentation, I found that using a "begin once" block could help mitigate this issue. Specifically, I referred to the documentation here.To address the problem, I made the following change:
with conn.begin:
to the SQL loop in thedf_to_psql
function withininput_data_functions.py
.This change ensures that each transaction is properly managed within the
df_to_psql
function, which has resolved the SQL lock issues in my tests. The model now completes its run without encountering lock-related interruptions.Thank you for reviewing this request.