Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dhMVI-00008b-A8 for pgsql-performance@arkaria.postgresql.org; Mon, 14 Aug 2017 21:02:28 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dhMVH-00057B-EA for pgsql-performance@arkaria.postgresql.org; Mon, 14 Aug 2017 21:02:27 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dhMVH-00056w-2y for pgsql-performance@postgresql.org; Mon, 14 Aug 2017 21:02:27 +0000 Received: from mail-qt0-x22d.google.com ([2607:f8b0:400d:c0d::22d]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1dhMVE-0000ds-9f for pgsql-performance@postgresql.org; Mon, 14 Aug 2017 21:02:26 +0000 Received: by mail-qt0-x22d.google.com with SMTP id p3so58553282qtg.2 for ; Mon, 14 Aug 2017 14:02:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=pczwUC0KfFUqhZ1shQC9WvNb+dEW35trf/zmTS1xhXI=; b=aDS32NMBiwQrub0ApVUVooPytLA++drtBISAx/4UORJtDDZCX/FuNhj/yvVBxWnlaK YVWfHVARWkokxyhSKtMIIIJKKakI46MWYZ5EW6kkOZQNqzLG4HR3mS3RvERr55runZxt 3ycNcP3qRcPgwIMG00ZNlKYseg68t9qTjVuYel48ONSmu1IQ42ZODbFmbaFUUW60vjTd pfl//pCieTMz/5hFpVl11zLZ1YEMlWICBKp3C3/b8+4xoPbVL7IOdt4BfKfFGZ3iwHrT 4JCiXUIpqf/wCEU+pFMXx4vedcZFG1XM66WkRLrOFqtabXJjNzZG5xKZkibQkKiNruaN LTpg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=pczwUC0KfFUqhZ1shQC9WvNb+dEW35trf/zmTS1xhXI=; b=puGkWZTApuCs5vS1WNnRbbEHKRy3MjW8MKMp4VMHyKvZ8DNCL36SmRMXHjivuqm4zt xyQPjiLqNyus9V00leWJOC7RZP5c7hHMP6lTsOz3sxVgo/OWOm42GzRyF+0zc8C+qmrt KHE0T2oorT5PQXRLBbRN1Uh89VwHqgYJfIGlsCJQIXnQ1ULPNP0MNoqMifZ9lRyLwdOt xVWW1Nb3nlwsmXRLqAsUCrZazNWw/xbRVvcZBqolt5Etsxi+TJezgA7HjZyEGLJOdjJO cFwZYJXbvqT5XJZyG28ymw2CipGASBBn3YYbemQncOk+0cMVRs+aLwBe9wBqsSTnp1ma feJw== X-Gm-Message-State: AHYfb5gS+DjHEfw1+ZJkyVA0ZNGkEjtLUJF89jRNs+/wYIY1CSxUvLbj YleAkhT0TY3E8WYxZH647LJPoKaUUA== X-Received: by 10.237.53.169 with SMTP id c38mr32807865qte.191.1502744542873; Mon, 14 Aug 2017 14:02:22 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.105.164 with HTTP; Mon, 14 Aug 2017 14:02:22 -0700 (PDT) In-Reply-To: References: From: Scott Marlowe Date: Mon, 14 Aug 2017 15:02:22 -0600 Message-ID: Subject: Re: Odd sudden performance degradation related to temp object churn To: Jeremy Finzel Cc: postgres performance list Content-Type: text/plain; charset="UTF-8" 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 Also if you're using newly loaded data the db could be setting hint bits on the first select etc. -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance