Re: solaris build problem with Sun compilers

Alan Stange <stange(at)rentec(dot)com> writes:
> Hmmm. I've just been looking at the last snapshot of the HEAD and
> s_lock.h is still using an ldstub instruction instead of a cas for the
> inlined tas() function when gcc is being used. Having a cas
> instruction here would probably be an improvement too, right?

[ shrug... ] The person who submitted the solaris_sparc.s change failed
to provide any evidence that it was anything but cosmetic, so I didn't
worry about changing the equivalent gcc code. If there's actually a
performance win, please cite chapter and verse. Also, shouldn't we be
worrying about breaking older Sparc chips? Does CAS go all the way
back?

> Finally, I noticed that pg_sleep is calling select() for a sleep. On
> Solaris, this is a fairly expensive way to get off the run queue
> compared to just calling nanosleep(). How often do backends go to
> sleep here under "typical" workloads?

If you actually reach that syscall you're screwed performance-wise
anyhow. I'm disinclined to mess with OS-specific variants of the
delay logic.

regards, tom lane