aboutsummaryrefslogtreecommitdiff
path: root/src/interfaces/libpq/fe-secure-gssapi.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2021-01-08 18:12:07 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2021-01-08 18:12:07 -0500
commit39d4a153105f0693d93f593a23e5144e2bd031ef (patch)
tree411628d9a8cd4e8a966af7ba4cf012cfdbb04bd9 /src/interfaces/libpq/fe-secure-gssapi.c
parentafcc8772edcec687d87b6f762ca6113229af7291 (diff)
downloadpostgresql-39d4a153105f0693d93f593a23e5144e2bd031ef.tar.gz
postgresql-39d4a153105f0693d93f593a23e5144e2bd031ef.zip
Fix plpgsql tests for debug_invalidate_system_caches_always.
Commit c9d529848 resulted in having a couple more places where the error context stack for a failure varies depending on debug_invalidate_system_caches_always (nee CLOBBER_CACHE_ALWAYS). This is not very surprising, since we have to re-parse cached plans if the plan cache is clobbered. Stabilize the expected test output by hiding the context stack in these places, as we've done elsewhere in this test script. (Another idea worth considering, now that we have debug_invalidate_system_caches_always, is to force it to zero for these test cases. That seems like it'd risk reducing the coverage of cache-clobber testing, which might or might not be worth being able to verify that we get the expected error output in normal cases. For the moment I just stuck with the existing technique.) In passing, update comments that referred to CLOBBER_CACHE_ALWAYS. Per buildfarm member hyrax.
Diffstat (limited to 'src/interfaces/libpq/fe-secure-gssapi.c')
0 files changed, 0 insertions, 0 deletions