Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtp (Exim 4.84_2)
	(envelope-from <pgsql-performance-owner+archive@lists.postgresql.org>)
	id 1eIH10-0003mK-JN
	for pgsql-performance@arkaria.postgresql.org; Fri, 24 Nov 2017 16:39:46 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.84_2)
	(envelope-from <pgsql-performance-owner+archive@lists.postgresql.org>)
	id 1eIH0w-00072Y-4Z
	for pgsql-performance@arkaria.postgresql.org; Fri, 24 Nov 2017 16:39:42 +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 <tgl@sss.pgh.pa.us>)
	id 1eIH0v-00072O-R7
	for pgsql-performance@lists.postgresql.org; Fri, 24 Nov 2017 16:39:41 +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.89)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1eIH0s-0004J6-HP
	for pgsql-performance@postgresql.org; Fri, 24 Nov 2017 16:39:40 +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 vAOGdZYj028357;
	Fri, 24 Nov 2017 11:39:36 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dmitry Shalashov <skaurus@gmail.com>
cc: "pgsql-performance@postgresql.org" <pgsql-performance@postgresql.org>
Subject: Re: Query became very slow after 9.6 -> 10 upgrade
In-reply-to: 
 <CAKPeCUF_k9dLot=Lb0anZZQZmjoS72ScSWr6oj9GCj_C3+Ciaw@mail.gmail.com>
References: 
 <CAKPeCUGAeHgoh5O=SvcQxREVkoX7UdeJUMj1F5=aBNvoTa+O8w@mail.gmail.com>
 <13426.1511363963@sss.pgh.pa.us>
 <CAKPeCUGkCcp37oa3n=-9EDAujx_f190wFdmbfy_K4OF5H62JyQ@mail.gmail.com>
 <9755.1511392027@sss.pgh.pa.us>
 <CAKPeCUEy6HMm=Kn=V82xjycZf9KYnqzPLVQ8ngjoLXvO97zx4g@mail.gmail.com>
 <5549.1511456440@sss.pgh.pa.us>
 <CAKPeCUF_k9dLot=Lb0anZZQZmjoS72ScSWr6oj9GCj_C3+Ciaw@mail.gmail.com>
Comments: In-reply-to Dmitry Shalashov <skaurus@gmail.com>
	message dated "Fri, 24 Nov 2017 18:44:21 +0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <28355.1511541575.1@sss.pgh.pa.us>
Date: Fri, 24 Nov 2017 11:39:35 -0500
Message-ID: <28356.1511541575@sss.pgh.pa.us>
List-Id: <pgsql-performance.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-performance@lists.postgresql.org>
List-Owner: <mailto:pgsql-performance-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-performance>
Precedence: bulk

Dmitry Shalashov <skaurus@gmail.com> writes:
> It looks that patch helps us. Tom, thank you!
> I'm still testing it though, just in case.

Excellent, please follow up if you learn anything new.

> What are PostgreSQL schedule on releasing fixes like this? Can I expect
> that it will be in 10.2 and when can I expect 10.2, approximately of course?

I haven't pushed it to the git repo yet, but I will shortly, and then
it will be in the next minor release.  That will probably be in
early February, per our release policy:
https://www.postgresql.org/developer/roadmap/

			regards, tom lane