aboutsummaryrefslogtreecommitdiff
path: root/contrib/btree_gist/btree_bit.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:51:08 -0500
commit8a2f783cc489e4e1820163c1c439125aad4d7a92 (patch)
treec054ee8bd08ffc3f0c8ede4b3548e774e1985242 /contrib/btree_gist/btree_bit.c
parent0ae4e49fa66342b7c6294a6534db51284f5385b7 (diff)
downloadpostgresql-8a2f783cc489e4e1820163c1c439125aad4d7a92.tar.gz
postgresql-8a2f783cc489e4e1820163c1c439125aad4d7a92.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 'contrib/btree_gist/btree_bit.c')
0 files changed, 0 insertions, 0 deletions