Re: How to specify/mock the statistic data of tables in PostgreSQL
| От | Atri Sharma |
|---|---|
| Тема | Re: How to specify/mock the statistic data of tables in PostgreSQL |
| Дата | |
| Msg-id | 66B7D041-6C4B-407E-B0AA-66AB26716144@gmail.com обсуждение исходный текст |
| Ответ на | Re: How to specify/mock the statistic data of tables in PostgreSQL ("ygnhzeus" <ygnhzeus@gmail.com>) |
| Ответы |
Re: How to specify/mock the statistic data of tables in PostgreSQL
|
| Список | pgsql-general |
Sent from my iPad
body{FONT-SIZE:12pt; FONT-FAMILY:宋体,serif;}
Thanks for your reply.
So correlation is not related to the calculation of selectivity right? If I force PostgreSQL not to optimize the join order (by setting join_collapse_limit and from_collapse_limit to 1) , is there any other factor that may affect the structure of execution plan regardless of the data access method.
2014-01-10
ygnhzeus
发件人：Amit Langote <amitlangote09@gmail.com>
发送时间：2014-01-10 22:00
主题：Re: [GENERAL] How to specify/mock the statistic data of tables in PostgreSQL
收件人："ygnhzeus"<ygnhzeus@gmail.com>
抄送："pgsql-general"<pgsql-general@postgresql.org>
AFAIK, correlation is involved in calculation of the costs that are used for deciding the type of access.If the correlation is low, index scan can lead to quite some random reads, hence leading to higher costs.
Regards,
Atri
В списке pgsql-general по дате отправления: