wieck@debis.com (Jan Wieck) writes:
> The ugly detail, I'm currently running into, is that there
> already seems to be a concurrency problem I discovered with
> my testing. Occationally I get this into the postmaster log
> for parallel executing tests:
> ERROR: Bad boolean external representation 'XXX'
> FATAL 1: SearchSysCache: recursive use of cache 10
> FATAL 2: elog: error in postmaster or backend startup, giving up!
> pq_flush: send() failed: Broken pipe
> Server process (pid 9791) exited with status 512 at Fri Nov 19 03:17:09 1999
> Terminating any active server processes...
> It happens during the first parallel group of 11 tests. Not
> allways, so it's timing critical. Outch.
In other words, you've already exposed a bug! Right on!
Commit the thing, so more eyes can look for the problem. I expect
you have found a pre-existing backend bug, not a problem in your
new regress test scaffold.
regards, tom lane