Increase WIDTH_THRESHOLD from 256 to 1K. This addresses recent observation

that ANALYZE would not gather any stats for a CHAR(255) column.  I still
think a width threshold is appropriate for the reasons mentioned in the
code, but we can loosen it at least.

diff --git a/src/backend/commands/analyze.c b/src/backend/commands/analyze.c
index 0d3173e9b3e9dd9a087a3184245864c7f958b3a9..2d9a2daa0cb5e38526a8ca246b7ba445fa6e6951 100644 (file)
--- a/src/backend/commands/analyze.c
+++ b/src/backend/commands/analyze.c
@@ -8,7 +8,7 @@
  *
  *
  * IDENTIFICATION
- *       $Header: /cvsroot/pgsql/src/backend/commands/analyze.c,v 1.44 2002/08/26 17:53:57 tgl Exp $
+ *       $Header: /cvsroot/pgsql/src/backend/commands/analyze.c,v 1.45 2002/08/26 18:45:57 tgl Exp $
  *
  *-------------------------------------------------------------------------
  */
@@ -56,7 +56,7 @@ typedef enum
  * ignoring wide values will not affect our estimates of histogram bin
  * boundaries very much.
  */
-#define WIDTH_THRESHOLD  256
+#define WIDTH_THRESHOLD  1024
 
 /*
  * We build one of these structs for each attribute (column) that is to be