-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set idle_in_transaction_session_timeout to 0 #198
base: master
Are you sure you want to change the base?
Conversation
statement_timeout is being set to 0 in session preventing failures when this parameter is non-zero. This change is to prevent failures due to idle-in-transaction timeout, which look like this: ``` FATAL: terminating connection due to idle-in-transaction timeout ERROR: query failed: server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. DETAIL: query was: SAVEPOINT repack_sp1 ```
I don't know why tests don't go thru -- please review it in general. Looking forward to feedback. |
The tests fail with:
The test script does:
It seems the error is not related to pg_repack, but to the database configuration for which a the user can't access the |
@dvarrazzo thank you. However the problem with tests is a bit more complicated – check out this https://travis-ci.org/reorg/pg_repack/jobs/477749374:
Any reasons to use a non-superuser role in tests? And can you help to fix tests here? |
@dvarrazzo kindly pinging you about the questions above |
I'm sorry I don't have resources now to look into this. |
@NikolayS Can you please rebase the PR? This will also trigger the GitHub Actions checks. Thanks. |
statement_timeout is being set to 0 in session preventing failures
when this parameter is non-zero. This change is to prevent failures due
to idle-in-transaction timeout, which look like this:
TODO:
idle_in_transaction_session_timeout
was added only in Postgres 9.6)