pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: pasman pasmański <pasman.p@gmail.com>
To: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Why we don't want hints Was: Slow count(*) again...
Date: Sun, 5 Jun 2011 16:25:39 +0100
Message-ID: <BANLkTimE3isrTRmZFG8obsvYJCUxSmJzaA@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimjt7PGuSyXFsedjCsANzMiVYNDfUUaPJ6_wqrr@mail.gmail.com>
References: <4D53CA4F020000250003A789@gw.wicourts.gov>
	<201102162122.p1GLMQS29138@momjian.us>
	<AANLkTimjt7PGuSyXFsedjCsANzMiVYNDfUUaPJ6_wqrr@mail.gmail.com>

Hi. I have the idea: hints joined to function. For example instead of

WHERE table1.field1=table2.field2
write:
WHERE specificeq(table1.field1,table2.field2)

and hints add to declaration of specificeq function.

2011/2/23, Robert Haas <robertmhaas@gmail.com>:
> On Wed, Feb 16, 2011 at 4:22 PM, Bruce Momjian <bruce@momjian.us> wrote:
>> I am not excited about the idea of putting these correlations in
>> queries.  What would be more intesting would be for analyze to build a
>> correlation coeffficent matrix showing how columns are correlated:
>>
>>        a   b   c
>>    a   1   .4  0
>>    b   .1  1   -.3
>>    c   .2  .3  1
>>
>> 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
>


-- 
------------
pasman



view thread (26+ messages)  latest in thread

Message-ID: <BANLkTimE3isrTRmZFG8obsvYJCUxSmJzaA@mail.gmail.com>
Permalink:  ../BANLkTimE3isrTRmZFG8obsvYJCUxSmJzaA@mail.gmail.com/
Also on:    postgresql.org/message-id/BANLkTimE3isrTRmZFG8obsvYJCUxSmJzaA@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: pasman.p@gmail.com
  Subject: Re: Why we don't want hints Was: Slow count(*) again...
  In-Reply-To: <BANLkTimE3isrTRmZFG8obsvYJCUxSmJzaA@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox