Re: estemated number of rows and optimiser effeciency

From: "David Johnston" <polobo(at)yahoo(dot)com>
To: "'salah jubeh'" <s_jubeh(at)yahoo(dot)com>, "'pgsql'" <pgsql-general(at)postgresql(dot)org>
Subject: Re: estemated number of rows and optimiser effeciency
Date: 2012-09-26 14:41:46
Message-ID: 00dc01cd9bf5$0e79d290$2b6d77b0$@yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>>  I am wondering, why the historical data (real result of the query) does
not affect the execution plan. For example, If I ran the query 10 times I
always get around 6500 instead of 5.5 million in the top most execution plan
node.

The likely accurate, if cheeky, answer is simply that no one has taken the
time to implement what at face value would seem to be an extremely complex
behavior.

As to the rest you should probably gather up some additional details and
post this over on performance. There is likely a middle ground between your
idea and the status quo but that ground cannot be evaluated unless examples
of possibly misbehaving queries are provided.

David J.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message salah jubeh 2012-09-26 14:51:26 Re: estemated number of rows and optimiser effeciency
Previous Message fra2012 2012-09-26 14:39:54 Server doesn't accept connection