Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1agbb5-00081H-60 for pgsql-performance@arkaria.postgresql.org; Thu, 17 Mar 2016 17:20:31 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1agbb4-0004kc-MG for pgsql-performance@arkaria.postgresql.org; Thu, 17 Mar 2016 17:20:30 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1agbb3-0004hj-D8 for pgsql-performance@postgresql.org; Thu, 17 Mar 2016 17:20:29 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1agbb1-0008UG-1A for pgsql-performance@postgresql.org; Thu, 17 Mar 2016 17:20:28 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id u2HHKNZS002280; Thu, 17 Mar 2016 13:20:23 -0400 From: Tom Lane To: Evgeniy Shishkin cc: Andreas Joseph Krogh , pgsql-performance Subject: Re: Searching GIN-index (FTS) and sort by timestamp-column In-reply-to: <1C0DB3A7-0933-4931-8585-AEBA88151C4E@gmail.com> References: <27201.1458135447@sss.pgh.pa.us> <9D98454D-D4E5-457F-8F5C-F49526BFA9FA@gmail.com> <1C0DB3A7-0933-4931-8585-AEBA88151C4E@gmail.com> Comments: In-reply-to Evgeniy Shishkin message dated "Wed, 16 Mar 2016 18:07:56 +0300" Date: Thu, 17 Mar 2016 13:20:23 -0400 Message-ID: <2279.1458235223@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org Evgeniy Shishkin writes: > Uh, it works if i cast to bigint explicitly FWIW, the reason for that is that the int8_ops operator class that btree_gin creates doesn't contain any cross-type operators. Probably wouldn't be that hard to fix if somebody wanted to put in the work. 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