* Tom Lane (tgl@sss.pgh.pa.us) wrote:
> I'm starting to think that we might have to succumb to having a compile
> option "optimize for multiprocessor" or "optimize for single processor".
> It's pretty hard to see how we'd alter a data structure decision like
> this on the fly.
I'd really hate to see this happen. In this case I don't think the
change you're proposing would have much of an impact on a uniprocessor
machine. Having seperate compile-time options for uniprocessor and
multiprocessor would open the gates for potentially other changes which
*would* have a more serious impact on one or the other when compiled for
the opposite. I think this would be a serious problem for binary
distributions and correspondingly their users.
Happy to test these changes, btw.
Also, I'm redoing my tests from the other patches with all the various
combinations; I'm a bit concerned that the recompiles I did (which were
just 'make', not 'make clean', 'make') for them previously didn't
actually recompile everything necessary. Sorry if the results differ.
Hope to have that all done this evening.
Thanks,
Stephen