Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 315F7477198 for ; Fri, 24 Jan 2003 16:02:16 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 5F894476B41 for ; Fri, 24 Jan 2003 15:22:27 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.6/8.12.6) with ESMTP id h0OKML5u021094; Fri, 24 Jan 2003 15:22:21 -0500 (EST) To: Ron Mayer Cc: Stephan Szabo , pgsql-performance@postgresql.org Subject: Re: Does "correlation" mislead the optimizer on large In-reply-to: References: Comments: In-reply-to Ron Mayer message dated "Fri, 24 Jan 2003 12:04:12 -0800" Date: Fri, 24 Jan 2003 15:22:21 -0500 Message-ID: <21093.1043439741@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/291 X-Sequence-Number: 938 Ron Mayer writes: > A proposal.... (yes I I'm volunteering if people point me in the right > direction)... would be to have a "plugable" set of analyze functions so that a > huge database that runs analyze infrequently could choose to have a very slow > analyze that might work better for it's data. I do not think ANALYZE is the problem here; at least, it's premature to worry about that end of things until you've defined (a) what's to be stored in pg_statistic, and (b) what computation the planner needs to make to derive a cost estimate given the stats. regards, tom lane