Skip site navigation (1) Skip section navigation (2)

Re: Planner not using column limit specified for one column for another column equal to first

From: Віталій Тимчишин <tivv00(at)gmail(dot)com>
To: Yeb Havinga <yebhavinga(at)gmail(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Planner not using column limit specified for one column for another column equal to first
Date: 2010-04-16 13:58:22
Message-ID: u2s331e40661004160658s842c95d4x22d212dc8cdbbb4e@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-performance
16 квітня 2010 р. 16:21 Yeb Havinga <yebhavinga(at)gmail(dot)com> написав:

> Віталій Тимчишин wrote:
>
>>
>> BTW: Changing slow query to inner joins do not make it fast
>>
> I'm interested to see the query andplan of the slow query with inner joins.
>
>
> Here you are. The query:

select * from company this_ inner join company_tag this_1_ on
this_.id=this_1_.company_id
inner join company_measures companymea2_ on
this_.id=companymea2_.company_id
inner join company_descr ces3_ on this_.id=ces3_.company_id
where this_1_.tag_id = 7 and this_.id>50000000
order by this_.id asc
limit 1000
;
Total runtime: 14088.942 ms
(plan is attached)

Best regards, Vitalii Tymchyshyn

Attachment: innerplan.txt
Description: text/plain (1.5 KB)

In response to

pgsql-performance by date

Next:From: Tom LaneDate: 2010-04-16 14:19:47
Subject: Re: Planner not using column limit specified for one column for another column equal to first
Previous:From: Yeb HavingaDate: 2010-04-16 13:21:30
Subject: Re: Planner not using column limit specified for one column for another column equal to first

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group