diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2016-08-25 09:57:09 -0400 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2016-08-25 09:57:21 -0400 |
commit | e6bd440688af13449bcb1b80698e6ef4b16245a6 (patch) | |
tree | f26a02c4868fb7b2f2761d5223be9e3a53e998d3 /src/backend/access/gist/gistget.c | |
parent | 006fb80a569179d3df4932857818925667e8d581 (diff) | |
download | postgresql-e6bd440688af13449bcb1b80698e6ef4b16245a6.tar.gz postgresql-e6bd440688af13449bcb1b80698e6ef4b16245a6.zip |
Fix instability in parallel regression tests.
Commit f0c7b789a added a test case in case.sql that creates and then drops
both an '=' operator and the type it's for. Given the right timing, that
can cause a "cache lookup failed for type" failure in concurrent sessions,
which see the '=' operator as a potential match for '=' in a query, but
then the type is gone by the time they inquire into its properties.
It might be nice to make that behavior more robust someday, but as a
back-patchable solution, adjust the new test case so that the operator
is never visible to other sessions. Like the previous commit, back-patch
to all supported branches.
Discussion: <5983.1471371667@sss.pgh.pa.us>
Diffstat (limited to 'src/backend/access/gist/gistget.c')
0 files changed, 0 insertions, 0 deletions