From: Tom Lane <tgl@sss.pgh.pa.us>
To: Huang, Suya <Suya.Huang@au.experian.com>
Cc: Andreas Kretschmer <akretschmer@spamfence.net>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: GIN index not used
Date: Fri, 11 Jul 2014 01:43:24 -0400
Message-ID: <21821.1405057404@sss.pgh.pa.us> (raw)
In-Reply-To: <D83E55F5F4D99B4A9B4C4E259E6227CD014C32C9@AUX1EXC01.apac.experian.local>
References: <D83E55F5F4D99B4A9B4C4E259E6227CD014C3263@AUX1EXC01.apac.experian.local>
<20140711044452.GA7390@tux>
<20680.1405054574@sss.pgh.pa.us>
<D83E55F5F4D99B4A9B4C4E259E6227CD014C32C9@AUX1EXC01.apac.experian.local>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
"Huang, Suya" <Suya.Huang@au.experian.com> writes:
> Just found out something here http://www.postgresql.org/message-id/17021.1234474178@sss.pgh.pa.us
> So I dropped the index and recreate it by specifying: using gin(terms_ts gin__int_ops) and the index works.
Oh, you're using contrib/intarray?
Pursuant to the thread you mention above, we removed intarray's <@ and @>
operators (commit 65e758a4d3) but then reverted that (commit 156475a589)
because of backwards-compatibility worries. It doesn't look like anything
got done about it since then. Perhaps the extension upgrade
infrastructure would offer a solution now.
> My PG version is 9.3.4, none-default planner settings:
> enable_mergejoin = off
> enable_nestloop = off
[ raised eyebrow... ] It's pretty hard to see how those would be
a good idea. Not all problems are best solved by hash joins.
regards, tom lane
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, Suya.Huang@au.experian.com, akretschmer@spamfence.net
Subject: Re: GIN index not used
In-Reply-To: <21821.1405057404@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox