| From: | Emre Hasegeli <emre(at)hasegeli(dot)com> |
|---|---|
| To: | "Huang, Suya" <Suya(dot)Huang(at)au(dot)experian(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andreas Kretschmer <akretschmer(at)spamfence(dot)net>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: GIN index not used |
| Date: | 2014-07-12 08:31:15 |
| Message-ID: | 20140712083115.GA515@hasegeli-2.local |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
> -----Original Message-----
It is hard to read your message. You should indicate the quoted lines.
Please fix your email client.
> About the contrib/intarray, do I have other choices not using that one?
integer[] and contrib/intarray are two different data types.
> About the join, yeah, in our testing for DW-like queries, hash join does improved the performance greatly...
Then, it should be chosen by the planner. I doubt it is the best
choice in all cases. It is not advised to set these parameters
globally.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magers, James | 2014-07-13 22:55:42 | Query Performance question |
| Previous Message | Kevin Grittner | 2014-07-11 13:19:09 | Re: 60 core performance with 9.3 |