On Fri, 12 Sep 2003, Bruce Momjian wrote:
> Marc G. Fournier wrote: > > > > > > On Thu, 11 Sep 2003, Bruce Momjian wrote: > > > > > Well, the problem was that we defined HAS_TEST_AND_SET inside the ports. > > > I guess we could splatter a test for Itanium and Opterion in every port > > > that could possibly use it, but then again, if we fall back to not > > > finding it for some reason, we don't get a report because we silently > > > fall back to semaphores. That's what has me worried, that if we don't > > > do it, we will not know what platforms really aren't working properly. > > > > >From what I understand, "not working properly" means slow, not broken, no? > > Which means ppl could submit a problem report and it could be fixed for > > v7.4.1 ... its not so much 'not working properly' as it is 'not optimal > > performance' ... > > Right, though I am not sure people will know _slow_ configuration vs. > PostgreSQL is slow. No, but definitely something for those discussion performance to add to their checklist :) BTW, post-compile, running system ... how do you check this? Or can you? For instance, having a checklist, of sorts, that ppl can go through when trying to investigate performance issues could include stuff like: check swap usage (albeit obvious to alot of ppl, not to all) check disk usage using iostat check spinlocks in use using ... ?? ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly