aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistvalidate.c
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2019-08-28 11:48:19 +0900
committerMichael Paquier <michael@paquier.xyz>2019-08-28 11:48:19 +0900
commitf51006ea9657d6fcad89298520f42071fcf2199e (patch)
tree9b52ad4759ec37547c32b49da7fb96b177d78cce /src/backend/access/gist/gistvalidate.c
parent8635d73e2f2297820751e725c0c8a01e507cf951 (diff)
downloadpostgresql-f51006ea9657d6fcad89298520f42071fcf2199e.tar.gz
postgresql-f51006ea9657d6fcad89298520f42071fcf2199e.zip
Disable timeouts when running pg_rewind with online source cluster
In this case, the transfer uses a libpq connection, which is subject to the timeout parameters set at system level, and this can make the rewind operation suddenly canceled which is not good for automation. One workaround to such issues would be to use PGOPTIONS to enforce the wanted timeout parameters, but that's annoying, and for example pg_dump, which can run potentially long-running queries disables all types of timeouts. lock_timeout and statement_timeout are the ones which can cause problems now. Note that pg_rewind does not use transactions, so disabling idle_in_transaction_session_timeout is optional, but it feels safer to do so for the future. This is back-patched down to 9.5. idle_in_transaction_session_timeout is only present since 9.6. Author: Alexander Kukushkin Discussion: https://postgr.es/m/CAFh8B=krcVXksxiwVQh1SoY+ziJ-JC=6FcuoBL3yce_40Es5_g@mail.gmail.com Backpatch-through: 9.5
Diffstat (limited to 'src/backend/access/gist/gistvalidate.c')
0 files changed, 0 insertions, 0 deletions