Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cvvwL-0002pO-5v for pgsql-performance@arkaria.postgresql.org; Thu, 06 Apr 2017 01:10:21 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cvvwK-0004yt-P9 for pgsql-performance@arkaria.postgresql.org; Thu, 06 Apr 2017 01:10:20 +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 1cvvuY-0007SH-LJ for pgsql-performance@postgresql.org; Thu, 06 Apr 2017 01:08:30 +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 1cvvuW-0001K6-G9 for pgsql-performance@postgresql.org; Thu, 06 Apr 2017 01:08:29 +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 v3618Pw7010943; Wed, 5 Apr 2017 21:08:25 -0400 From: Tom Lane To: rverghese cc: pgsql-performance@postgresql.org Subject: Re: -EXT-Re: Table not using tsvector gin index and performance much worse than when it uses it. In-reply-to: <1491438412093-5954509.post@n3.nabble.com> References: <1491432671098-5954485.post@n3.nabble.com> <5326.1491434397@sss.pgh.pa.us> <1491436440096-5954503.post@n3.nabble.com> <1491438412093-5954509.post@n3.nabble.com> Comments: In-reply-to rverghese message dated "Wed, 05 Apr 2017 17:26:52 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <10941.1491440905.1@sss.pgh.pa.us> Date: Wed, 05 Apr 2017 21:08:25 -0400 Message-ID: <10942.1491440905@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 rverghese writes: > Will play around with those settings as well. Maybe start with default which > is 50 I believe. If you're on 9.5, auto-analyze does not result in a pending list flush, so it's irrelevant to fixing your problem. (Assuming I've identified the problem correctly.) But you do have gin_pending_list_limit, so see what that does for you. Note you can set it either globally or per-index. 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