Search Postgresql Archives

Re: judging acceptable discrepancy in row count v. estimate

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




> On Oct 16, 2018, at 1:01 PM, Tom Lane <tgl@xxxxxxxxxxxxx> wrote:
> 
> Rob Sargent <robjsargent@xxxxxxxxx> writes:
>> Should reality be half again as large as the estimated row count?
>> coon=# select count(*) from sui.segment;
>>  count   
>> ----------
>> 49,942,837  -- my commas
>> (1 row)
> 
>> coon=# vacuum (analyse, verbose) sui.probandset;
> 
> Uh, what does sui.probandset have to do with sui.segment ?
> 
> 			regards, tom lane

In fullness, 

INFO:  analyzing "sui.segment"
INFO:  "segment": scanned 30000 of 1019242 pages, containing 1470000 live rows and 0 dead rows; 30000 rows in sample, 49942858 estimated total rows
VACUUM
Time: 321934.748 ms (05:21.935)

So, rather accurately estimated (no inserts, deletes) since bogus report.  Looks like its good to 5+ decimal places, given sufficient records.

select 49942858.0/49942837.0;
        ?column?        
------------------------
 1.00000042048071878656
(1 row)

This table has no variable length columns. I imagine that helps.






[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]

  Powered by Linux