Re: Better default_statistics_target

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Greg Sabino Mullane" <greg(at)turnstep(dot)com>, <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Better default_statistics_target
Date: 2007-11-19 08:15:17
Message-ID: 87ejemvega.fsf@oxford.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

"Simon Riggs" <simon(at)2ndquadrant(dot)com> writes:

> Long text fields that might use LIKE should be set to 100. CHAR(1) and
> general fields should be set to 10.

I could see arguing that either way. Longer fields are capable of more
precision and so may need more buckets to predict. On the other hand longer
fields take more space and take longer to compare so to make consistent use of
resources you would want to avoid storing and comparing large numbers of them
whereas you could afford much larger targets for small quick columns.

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Page 2007-11-19 08:31:57 Server maintenance
Previous Message Matt Magoffin 2007-11-19 07:52:22 possible to create multivalued index from xpath() results in 8.3?

Browse pgsql-patches by date

  From Date Subject
Next Message Andrew Dunstan 2007-11-19 13:31:43 Re: [HACKERS] fulltext parser strange behave
Previous Message Simon Riggs 2007-11-18 14:42:54 Re: Better default_statistics_target