summaryrefslogtreecommitdiff
path: root/contrib/btree_gist/btree_gist.c
diff options
context:
space:
mode:
authorJacob Champion <jchampion@postgresql.org>2025-08-08 08:44:56 -0700
committerJacob Champion <jchampion@postgresql.org>2025-08-08 08:44:56 -0700
commit3e311664e4974ea0eef708d54256aacbb0239c95 (patch)
tree0daf121fc121264131f6952233d8b674216eed2b /contrib/btree_gist/btree_gist.c
parent1749a12f0d2005ba23236089f0a32e6c6c1533f0 (diff)
oauth: Track total call count during a client flow
Tracking down the bugs that led to the addition of comb_multiplexer() and drain_timer_events() was difficult, because an inefficient flow is not visibly different from one that is working properly. To help maintainers notice when something has gone wrong, track the number of calls into the flow as part of debug mode, and print the total when the flow finishes. A new test makes sure the total count is less than 100. (We expect something on the order of 10.) This isn't foolproof, but it is able to catch several regressions in the logic of the prior two commits, and future work to add TLS support to the oauth_validator test server should strengthen it as well. Backpatch-through: 18 Discussion: https://postgr.es/m/CAOYmi+nDZxJHaWj9_jRSyf8uMToCADAmOfJEggsKW-kY7aUwHA@mail.gmail.com
Diffstat (limited to 'contrib/btree_gist/btree_gist.c')
0 files changed, 0 insertions, 0 deletions