Andres Freund <and...@anarazel.de> writes:
> I'm not wild to go for a separate TAP test. A separate initdb cycle for
> a a tests that takes about 30ms seems a bit over the top.
Fair enough.
> So I'm
> inclined to either try running it in a serial step on the buildfarm
> (survived a few dozen cycles with -DRELCACHE_FORCE_RELEASE
> -DCATCACHE_FORCE_RELEASE, and a few with -DCLOBBER_CACHE_ALWAYS), or
> just remove them alltogether. Or remove it alltogether until we fix
> this. Since you indicated a preference agains the former, I'll remove
> it in a bit until I hear otherwise.
> I'll add it to my todo list to try to fix the concurrency issues for 13.
If you're really expecting to have a go at that during the v13 cycle,
I think we could live without these test cases till then.
regards, tom lane
