From: | Sameer Kumar <sameer(dot)kumar(at)ashnik(dot)com> |
---|---|
To: | Adarsh Sharma <eddy(dot)adarsh(at)gmail(dot)com> |
Cc: | PostgreSQL General Discussion Forum <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Join Bad Performance on different data types |
Date: | 2014-03-04 07:43:42 |
Message-ID: | CADp-Sm5B8CV4uhBYsa6t+rjnEFDH4bcLk9=VpOgpwWgHTos+1Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Mar 4, 2014 at 2:57 PM, Adarsh Sharma <eddy(dot)adarsh(at)gmail(dot)com> wrote:
> I tried creating simple and gin indexes on the column(t_ids) but still not
> helping. Anyone has any idea or faced this before. Postgresql version is
> 9.2.
>
have you done a vacuum analyze or analyze after this step?
You might have to disable sequential scans
set enable_seqscan=off;
And then fire the query.
Best Regards,
*Sameer Kumar | Database Consultant*
*ASHNIK PTE. LTD.*
101 Cecil Street, #11-11 Tong Eng Building, Singapore 069533
M: *+65 8110 0350* T: +65 6438 3504 | www.ashnik.com
*[image: icons]*
[image: Email patch] <http://www.ashnik.com/>
This email may contain confidential, privileged or copyright material and
is solely for the use of the intended recipient(s).
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2014-03-04 07:48:38 | Re: Join Bad Performance on different data types |
Previous Message | Adarsh Sharma | 2014-03-04 06:57:50 | Join Bad Performance on different data types |