aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeModifyTable.c
diff options
context:
space:
mode:
authorRobert Haas <rhaas@postgresql.org>2023-02-06 10:51:08 -0500
committerRobert Haas <rhaas@postgresql.org>2023-02-06 10:55:42 -0500
commit98e7234242a652497c99d4d0d6f2bf9a75d4e921 (patch)
treebfa2d6d50199b5b4a7a1b0c8730bd26caab75e61 /src/backend/executor/nodeModifyTable.c
parentec16eac8dabcd80559dcc6aeec48c0b57fb8b2bd (diff)
downloadpostgresql-98e7234242a652497c99d4d0d6f2bf9a75d4e921.tar.gz
postgresql-98e7234242a652497c99d4d0d6f2bf9a75d4e921.zip
Disable STARTUP_PROGRESS_TIMEOUT in standby mode.
In standby mode, we don't actually report progress of recovery, but up until now, startup_progress_timeout_handler() nevertheless got called every log_startup_progress_interval seconds. That's an unnecessary expense, so avoid it. Report by Thomas Munro. Patch by Bharath Rupireddy, reviewed by Simon Riggs, Thomas Munro, and me. Back-patch to v15, where the problem was introduced. Discussion: https://www.postgresql.org/message-id/CA%2BhUKGKCHSffAj8zZJKJvNX7ygnQFxVD6wm1d-2j3fVw%2BMafPQ%40mail.gmail.com
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions