Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1i2DXL-0006yx-1B for pgsql-performance@arkaria.postgresql.org; Mon, 26 Aug 2019 11:51:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1i2DXI-00012f-EM for pgsql-performance@arkaria.postgresql.org; Mon, 26 Aug 2019 11:51:48 +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_SHA1:256) (Exim 4.89) (envelope-from ) id 1i2DXI-00012S-0H for pgsql-performance@lists.postgresql.org; Mon, 26 Aug 2019 11:51:48 +0000 Received: from mail-io1-xd41.google.com ([2607:f8b0:4864:20::d41]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1i2DXF-0002WU-OM for pgsql-performance@lists.postgresql.org; Mon, 26 Aug 2019 11:51:47 +0000 Received: by mail-io1-xd41.google.com with SMTP id t3so36431034ioj.12 for ; Mon, 26 Aug 2019 04:51:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=rNg3WHdJCFEXaiFjJrZCtp/hWq+zzPrylOve31NDiGw=; b=ZxQwxzji68tIAvhLh7CHs7a6G04gX7EvXGy4J7sIEj3wQKSzwtxIZSNX/eSwAyRnTb /dNom5S6qTp2S/WnEspb8H/VRpDc3Agck5qunoBzCg65854WAKLxEcXCBPKFn4MUXiaZ Mx8IMGgj+i2bxBXCP7nI6bS3fmAy9tW1BSaiX0qz37QZ3SxFCen/iZXI2E3GYcVTzyRL TarUVIj4YEN+JMPsaeoCBJIlGqPqRHRCikO79sW/W1KcB6zgY/QHLjugNj1vpSDIA//d biXRrJKpUK908U5VcIYPVNrf+eJ+9yvZz3Qs5v+uw1ZgRQn+S06JKrHp4T9NDeCVkeYe ulAw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=rNg3WHdJCFEXaiFjJrZCtp/hWq+zzPrylOve31NDiGw=; b=f5bhohmcIghQdcZwVqjolqcIP2NTB8E5K/wXxhpRx+D0Niv9lv/iN0saBp7b0Pi79X 7Q+nDJj9KXEKsh4Q1fq8NRCwSx3KOA9YlCGT5VsUblLx7bwiM3+jisGlgV/G30mq6UoW aTzT9b3j/qBsNe0QfxGMYPQ8iD922Xw6tsYx6u7H1J1zDsLOBC2Fue9GPs1ldaKzNfY3 MemF18YlLXsusdvrYiRnFYEBrVa0E5y99sZaXTIcEOX/ZaIJSH74fxyZUvzMCLcch+1I RdfZrpj6WFBIaWGUowivE0uv9tApz46JDfiZ1nKuqmm9qe52+4gJhDSDYH894/NOk+6b qZeg== X-Gm-Message-State: APjAAAUDH/p8VK7m2DUuHcOhsprK9C0y0bpZQ8O2mxmOApAKsIm9IO/R fmzZOTGfcvAKILg6yz5FBGBRKg== X-Google-Smtp-Source: APXvYqzl26fiV35JftLF/6KcJ31hZ3u5bFWPo7U+nlgs62WfjnesGg4Be/KJfgAkzRJxTiFBJsJKNQ== X-Received: by 2002:a5e:d803:: with SMTP id l3mr4688542iok.126.1566820303625; Mon, 26 Aug 2019 04:51:43 -0700 (PDT) Received: from pryzbyj (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id m67sm14811181iof.21.2019.08.26.04.51.42 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 26 Aug 2019 04:51:42 -0700 (PDT) Received: by pryzbyj (Postfix, from userid 1000) id 6AD678007F5; Mon, 26 Aug 2019 06:51:41 -0500 (CDT) Date: Mon, 26 Aug 2019 06:51:41 -0500 From: Justin Pryzby To: Barbu Paul - Gheorghe Cc: Jeff Janes , pgsql-performance@lists.postgresql.org Subject: Re: Erratically behaving query needs optimization Message-ID: <20190826115141.GE7201@telsasoft.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Mon, Aug 26, 2019 at 11:25:57AM +0300, Barbu Paul - Gheorghe wrote: > On Sun, Aug 25, 2019 at 5:51 PM Jeff Janes wrote: > > > You can use pg_rewarm to overcome the cold cache issue when you first start up the server. > > I cannot find anything related to pg_rewarm other than some dead ends > from 2013 from which I gather it only works on Linux. It's a current extension - spelled PREwarm, not rewarm, and definitely not reworm. https://www.postgresql.org/docs/current/pgprewarm.html