Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 47894B5DC1C for ; Sun, 5 Jun 2011 12:25:53 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 09010-05 for ; Sun, 5 Jun 2011 15:25:40 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-vw0-f46.google.com (mail-vw0-f46.google.com [209.85.212.46]) by mail.postgresql.org (Postfix) with ESMTP id 4BC38B5D800 for ; Sun, 5 Jun 2011 12:25:40 -0300 (ADT) Received: by vws1 with SMTP id 1so2288142vws.19 for ; Sun, 05 Jun 2011 08:25:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=lbEQuzJ5ZXtfntxpobSTKWC2JAoth5Oid/ddif5wzlo=; b=ltQd/iTzvUHwV8tfOZc04VIG+o5QQSCaiv0zhiebXNGYS2CHKPH732nOjs2Owoeopp xOvqk2Y9whAjuaUOvNMEhAOQxiB1ODcqA/AziJi6xinOL4gpr8wrtIX5ru8fo/tgdvKq stgxg2jit/IzHtQ1vIEQzsKVayRZ5sszojAzA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=w5oCvI4IsNgWpHY3gVtz6ZkrV0wkj03yUPF67JrCuLKGhZbFelUs7M3HRvtS+twzVI Ija0P2ljiFJ9z9GkCy9ZmmXvvzPJKje6n92ELT3Ib9vtwznz61pirL1d2zs2u6swXMG8 7hUTeO14dBjZneudnkndVdxOo38GCCoFFjwn4= MIME-Version: 1.0 Received: by 10.220.49.82 with SMTP id u18mr277976vcf.146.1307287539075; Sun, 05 Jun 2011 08:25:39 -0700 (PDT) Received: by 10.220.177.132 with HTTP; Sun, 5 Jun 2011 08:25:39 -0700 (PDT) In-Reply-To: References: <4D53CA4F020000250003A789@gw.wicourts.gov> <201102162122.p1GLMQS29138@momjian.us> Date: Sun, 5 Jun 2011 16:25:39 +0100 Message-ID: Subject: Re: Why we don't want hints Was: Slow count(*) again... From: =?ISO-8859-2?Q?pasman_pasma=F1ski?= To: "pgsql-performance@postgresql.org" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.898 tagged_above=-10 required=5 tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, RFC_ABUSE_POST=0.001 X-Spam-Level: X-Archive-Number: 201106/29 X-Sequence-Number: 43962 Hi. I have the idea: hints joined to function. For example instead of WHERE table1.field1=3Dtable2.field2 write: WHERE specificeq(table1.field1,table2.field2) and hints add to declaration of specificeq function. 2011/2/23, Robert Haas : > On Wed, Feb 16, 2011 at 4:22 PM, Bruce Momjian wrote: >> I am not excited about the idea of putting these correlations in >> queries. =A0What would be more intesting would be for analyze to build a >> correlation coeffficent matrix showing how columns are correlated: >> >> =A0 =A0 =A0 =A0a =A0 b =A0 c >> =A0 =A0a =A0 1 =A0 .4 =A00 >> =A0 =A0b =A0 .1 =A01 =A0 -.3 >> =A0 =A0c =A0 .2 =A0.3 =A01 >> >> and those correlations could be used to weigh how the single-column >> statistics should be combined. > > If you can make it work, I'll take it... it's (much) easier said than > done, though. > > -- > Robert Haas > EnterpriseDB: http://www.enterprisedb.com > The Enterprise PostgreSQL Company > > -- > Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org= ) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-performance > --=20 ------------ pasman