PostGIS  2.5.7dev-r@@SVN_REVISION@@

◆ gserialized_analyze_nd()

Datum gserialized_analyze_nd ( PG_FUNCTION_ARGS  )

Definition at line 1898 of file gserialized_estimate.c.

1899 {
1900  VacAttrStats *stats = (VacAttrStats *)PG_GETARG_POINTER(0);
1901  Form_pg_attribute attr = stats->attr;
1902 
1903  POSTGIS_DEBUG(2, "gserialized_analyze_nd called");
1904 
1905  /* If the attstattarget column is negative, use the default value */
1906  /* NB: it is okay to scribble on stats->attr since it's a copy */
1907  if (attr->attstattarget < 0)
1908  attr->attstattarget = default_statistics_target;
1909 
1910  POSTGIS_DEBUGF(3, " attribute stat target: %d", attr->attstattarget);
1911 
1912  /* Setup the minimum rows and the algorithm function.
1913  * 300 matches the default value set in
1914  * postgresql/src/backend/commands/analyze.c */
1915  stats->minrows = 300 * stats->attr->attstattarget;
1916  stats->compute_stats = compute_gserialized_stats;
1917 
1918  POSTGIS_DEBUGF(3, " minrows: %d", stats->minrows);
1919 
1920  /* Indicate we are done successfully */
1921  PG_RETURN_BOOL(true);
1922 }
static void compute_gserialized_stats(VacAttrStats *stats, AnalyzeAttrFetchFunc fetchfunc, int sample_rows, double total_rows)
In order to do useful selectivity calculations in both 2-D and N-D modes, we actually have to generat...

References compute_gserialized_stats().

Here is the call graph for this function: