Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Preventing delayed block cleanout due to loading a datawarehouse
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Randolf Geist  
View profile  
 More options Apr 20 2011, 5:37 am
Newsgroups: comp.databases.oracle.server
From: Randolf Geist <mah...@web.de>
Date: Wed, 20 Apr 2011 02:37:56 -0700 (PDT)
Local: Wed, Apr 20 2011 5:37 am
Subject: Re: Preventing delayed block cleanout due to loading a datawarehouse
On Apr 19, 2:51 pm, Donatello Settembrino

<donatello.settembr...@gmail.com> wrote:
> Exactly, that's right

By the way - we digress - my comment about PCTFREE is irrelevant in
this case since Oracle will stuff this row into a single block no
matter what the PCTFREE setting is as long as the row fits into the
block.

And: You don't have chained rows but your test case is flawed: A
select count(*) never reports "table fetch continued row" because it
does not have to visit the columns but only accesses the row entries
in the row directory. So even with chained rows your test will not
report any "table fetch continued row" statistics. You would need to
count/access a column that is part of the "chained" row pieces - and
it would have to be nullable, otherwise recent versions of Oracle will
transform a count(col) to a count(*).

Randolf


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.