On Tue, Dec 3, 2013 at 8:30 PM, Greg Stark <st...@mit.edu> wrote: > Worse, my experience with the posix_fadvise benchmarking is that on > spinning media reading one out of every 16 blocks takes about the same > time as reading them all. Presumably this is because the seek time > between tracks dominates and reading one out of every 16 blocks is > still reading every track. So in fact if your table is up to about > 3-4G ANALYZE is still effectively going to do a full table scan, at > least as far as I/O time goes.
Actually, it's rotational latency the dominant cost there. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
