Bruce Momjian writes:
> > Bruce Momjian <[EMAIL PROTECTED]> writes:
> >
> > > No, we have no ability to randomly pick rows to use for
> > > estimating statistics. Should we have this ability?
> >
> > That would be really slick, especially given the fact that VACUUM
> > runs much faster t
Bruce Momjian <[EMAIL PROTECTED]> writes:
>> I find it hard to believe that VAC ANALYZE is all that much slower than
>> plain VACUUM anyway; fixing the indexes is the slowest part of VACUUM in
>> my experience. It would be useful to know exactly what the columns are
>> in a table where VAC ANALYZ
> To get a partial VACUUM ANALYZE that was actually usefully faster than
> the current code, I think you'd have to read just a few percent of the
> blocks, which means much less than a few percent of the rows ... unless
> maybe you picked selected blocks but then used all the rows in those
> block
Bruce Momjian <[EMAIL PROTECTED]> writes:
>> How's reading a sufficiently large fraction of random rows going to be
>> significantly faster than reading all rows? If you're just going to read
>> the first n rows then that isn't really random, is it?
> Ingres did this too, I thought. You could s
Bruce Momjian <[EMAIL PROTECTED]> writes:
> No, we have no ability to randomly pick rows to use for estimating
> statistics. Should we have this ability?
That would be really slick, especially given the fact that VACUUM runs
much faster than VACUUM ANALYZE for a lot of PG users. I could change
> Bruce Momjian writes:
>
> > No, we have no ability to randomly pick rows to use for estimating
> > statistics. Should we have this ability?
>
> How's reading a sufficiently large fraction of random rows going to be
> significantly faster than reading all rows? If you're just going to read
>
Bruce Momjian writes:
> No, we have no ability to randomly pick rows to use for estimating
> statistics. Should we have this ability?
How's reading a sufficiently large fraction of random rows going to be
significantly faster than reading all rows? If you're just going to read
the first n rows
> Bruce Momjian <[EMAIL PROTECTED]> writes:
>
> > No, we have no ability to randomly pick rows to use for estimating
> > statistics. Should we have this ability?
>
> That would be really slick, especially given the fact that VACUUM runs
> much faster than VACUUM ANALYZE for a lot of PG users.
[ Charset ISO-8859-1 unsupported, converting... ]
> Hi,
>
> In Oracle, there are 2 ways to do the equivalent of vacuum analyze :
>
> * analyze table xx compute statitics
> * analyze table xx estimate statistics
>
> In the second form, you can tell on what percentage of the file you
> will do yo
