You realize that it had to be turned on explicitly on IRIX, right? But
don't let facts get in the way of a good rant...
On the contrary, with Irix 4 and earlier it was the default, but it caused so many problems that
SGI switched the default to OFF in IRIX 5. But because it had been available for so long, many
important apps had come to rely on it, so most sites had to immediately re-enable virtual swap on
every IRIX 5 server that came in. Admins just got used to doing it, so it became a
"default" at most sites, and admins often couldn't be convinced to disable it for
database server machines, because "That's our standard for IRIX configuration."
I worked at a big molecular modeling/visualization company; our visualization programs
*required* virtual swap, and our server programs *prohibited* virtual swap. Imagine how
our sales people felt about that, telling customers that they'd have to buy two $30,000
machines just because of one kernel parameter. Of course, they didn't, and our server
apps took the heat as being "unreliable."
SGI called it "virtual swap" which I always thought was a hoot. You have
virtual memory, which is really your swap space, and then virtual swap, which is some
kind of dark hole...
Craig
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
