RE: Doubt related to ROWID
- From: "Mark W. Farnham" <mwf@xxxxxxxx>
- To: <jonathan@xxxxxxxxxxxxxxxxxx>, "'Ric Van Dyke'" <ric.van.dyke@xxxxxxxxxx>, "'ORACLE-L'" <oracle-l@xxxxxxxxxxxxx>
- Date: Wed, 24 Jul 2013 15:49:50 -0400
Cannot resist: Mission Accomplished. As self-appointed judge of geek
contests I declare Jonathan has out-geeked Ric this time.
BTW, we ALL use clusters pretty much all the time:
OWNER CLUSTER_NAME
TABLESPACE_NAME
------------------------------ ------------------------------
------------------------------
SYS SMON_SCN_TO_TIME_AUX SYSAUX
SYS C_COBJ# SYSTEM
SYS C_FILE#_BLOCK# SYSTEM
SYS C_MLOG# SYSTEM
SYS C_OBJ# SYSTEM
SYS C_OBJ#_INTCOL# SYSTEM
SYS C_RG# SYSTEM
SYS C_TOID_VERSION# SYSTEM
SYS C_TS# SYSTEM
SYS C_USER# SYSTEM
If you want to go extra geeky, read the sql.bsq file (which I'm quite sure
both participants in the geekiest contest have done.) The comments about
what the v6 developers (architects?) thought would be sufficient size for
the number of columns of the day are hilarious. (And they were very very
smart persons, no doubt there. Changing times...)
mwf
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Jonathan Lewis
Sent: Wednesday, July 24, 2013 11:09 AM
To: Ric Van Dyke; ORACLE-L
Subject: RE: Doubt related to ROWID
Ric,
I know, I was just trying to out-geek you.
Regards
Jonathan Lewis
________________________________________
From: Ric Van Dyke [ric.van.dyke@xxxxxxxxxx]
Sent: 24 July 2013 16:07
To: Jonathan Lewis; ORACLE-L
Subject: RE: Doubt related to ROWID
Roger that, what I was more joking at was to not even get the row at all.
The fastest way to do anything is to not do it at all. ;-)
(My kids seem to have listen to me a bit too much on this point....)
===================
Ric Van Dyke
Education Director
Hotsos Enterprises LTD.
-----Original Message-----
From: Jonathan Lewis [mailto:jonathan@xxxxxxxxxxxxxxxxxx]
Sent: Wednesday, July 24, 2013 11:04 AM
To: Ric Van Dyke; ORACLE-L
Subject: Re: Doubt related to ROWID
Well,
You could avoid the LIO by using the result cache, but there are far fewer
latches on the result cache, so not doing the LIO might cause more
contention and therefore be more resource-intensive than doing the LIO
;)--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
