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:37 -0400 |
| commit | 68bd9f795d49603941527d1bf357f5e74d164ece (patch) | |
| tree | 2fa6ea0fee818dde2b4e98bfdc2693822d4f83c2 /src/backend/executor/nodeModifyTable.c | |
| parent | aaad96e4026e7bb3033ac0127510f2c60116a1b3 (diff) | |
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/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions