Re: How to specify/mock the statistic data of tables in PostgreSQL

From: Atri Sharma <atri(dot)jiit(at)gmail(dot)com>
To: ygnhzeus <ygnhzeus(at)gmail(dot)com>
Cc: Amit Langote <amitlangote09(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: How to specify/mock the statistic data of tables in PostgreSQL
Date: 2014-01-10 14:19:13
Message-ID: 66B7D041-6C4B-407E-B0AA-66AB26716144@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Sent from my iPad

> On 10-Jan-2014, at 19:42, "ygnhzeus" <ygnhzeus(at)gmail(dot)com> wrote:
>
> 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(at)gmail(dot)com>
> 发送时间:2014-01-10 22:00
> 主题:Re: [GENERAL] How to specify/mock the statistic data of tables in PostgreSQL
> 收件人:"ygnhzeus"<ygnhzeus(at)gmail(dot)com>
> 抄送:"pgsql-general"<pgsql-general(at)postgresql(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Amit Langote 2014-01-10 14:32:45 Re: How to specify/mock the statistic data of tables in PostgreSQL
Previous Message ygnhzeus 2014-01-10 14:12:49 Re: How to specify/mock the statistic data of tables in PostgreSQL