Re: estemated number of rows and optimiser effeciency - Mailing list pgsql-general

From David Johnston
Subject Re: estemated number of rows and optimiser effeciency
Date
Msg-id 00dc01cd9bf5$0e79d290$2b6d77b0$@yahoo.com
Whole thread Raw
In response to estemated number of rows and optimiser effeciency  (salah jubeh <s_jubeh@yahoo.com>)
Responses Re: estemated number of rows and optimiser effeciency
List 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.




pgsql-general by date:

Previous
From: fra2012
Date:
Subject: Server doesn't accept connection
Next
From: salah jubeh
Date:
Subject: Re: estemated number of rows and optimiser effeciency