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:09 -0400 |
commit | 2533ff0aa518d4d31391db279cf08e538fae5931 (patch) | |
tree | 3ff4dc345cd26a10bd2602ca0dd4e793b1159e5e /contrib/postgres_fdw/postgres_fdw.c | |
parent | ae4760d667c71924932ab32e14996b5be1831fc6 (diff) | |
download | postgresql-2533ff0aa518d4d31391db279cf08e538fae5931.tar.gz postgresql-2533ff0aa518d4d31391db279cf08e538fae5931.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 'contrib/postgres_fdw/postgres_fdw.c')
0 files changed, 0 insertions, 0 deletions