Re: Thoughts on statistics for continuously advancing columns - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Thoughts on statistics for continuously advancing columns
Date
Msg-id 9435.1262212502@sss.pgh.pa.us
Whole thread Raw
In response to Re: Thoughts on statistics for continuously advancing columns  (Chris Browne <cbbrowne@acm.org>)
List pgsql-hackers
Chris Browne <cbbrowne@acm.org> writes:
> I find it curious that ANALYZE *would* take a long time to run.

> After all, its sampling strategy means that, barring having SET
> STATISTICS to some ghastly high number, it shouldn't need to do
> materially more work to analyze a 1TB table than is required to analyze
> a 1GB table.

Right.  The example JD quotes in this thread compares a 35MB table
to a 350MB one, and the difference is all about having crossed the
threshold of what would fit in his available RAM.  There isn't going
to be much difference in the ANALYZE time for "big" versus "very big"
tables.  (There might, however, be a difference in the quality of
the resulting stats :-()
        regards, tom lane


pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: Thoughts on statistics for continuously advancing columns
Next
From: Hiroshi Inoue
Date:
Subject: Re: krb_server_keyfile setting doesn't work on Windows