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 1hBlZ6-0006kq-Tv for pgsql-general@arkaria.postgresql.org; Wed, 03 Apr 2019 19:28:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hBlZ5-000160-Lw for pgsql-general@arkaria.postgresql.org; Wed, 03 Apr 2019 19:28:51 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hBlZ5-00012X-7Y for pgsql-general@lists.postgresql.org; Wed, 03 Apr 2019 19:28:51 +0000 Received: from tamriel.snowman.net ([2001:470:e38f::11]) by makus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hBlZ2-00014Z-KL for pgsql-general@postgresql.org; Wed, 03 Apr 2019 19:28:49 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id 174B15F7A5; Wed, 3 Apr 2019 15:28:48 -0400 (EDT) Date: Wed, 3 Apr 2019 15:28:48 -0400 From: Stephen Frost To: Michael Lewis Cc: Jonathan Marks , pgsql-general Subject: Re: Forcing index usage Message-ID: <20190403192847.GH6197@tamriel.snowman.net> References: <679378F9-E085-4FE3-BC78-3073A4B86438@gmail.com> <20190403184425.GG6197@tamriel.snowman.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="/+tgMl2zofoPYNwo" 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 --/+tgMl2zofoPYNwo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Greetings, * Michael Lewis (mlewis@entrata.com) wrote: > Thanks for that advance warning since it is a handy option to force the > planning barrier in my experience. What's a resource to see other coming > changes in v12 especially changes to default behavior like this? Will there > be a new cte_collapse_limit setting or similar? Check the release notes. Thanks, Stephen --/+tgMl2zofoPYNwo Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJcpQlvAAoJEO1sijiDR2RVbf8QAJlCrqtkrMaDtEuS1nu0tZGu eKiQVDKQttQRqZCKebdHyXQS7Ffag1lrmGe4BJF3rg4tUUI+2/2TFFUId860+9yW A6AeS97s9J9u96PMqWFdzbRq+D5OYhzhfCtuiAPMKc5hpLcHxR6ODhjo4X3fft05 EO1j+EpXowVM0FZbfDvbaR/HLWE36kOoS2C5bvatqTG9U2Fv8e5l9FBueZokQ74u 9W/xnxZf1oogpCuWJSSMJKU4rsFM/dd7f6niNfLVv4E5SqUrF7lElT2bIw1lKOkj LTDRsr/cyqFNOIcB6dkJhM5HmcZIal/0zGGUUgcqXkKE3toXdkcW8WGPB9LjPht8 ajnlbINH3xNCR1mIbEFbpF4StpAPRiWfhAEFb3k34qUJjC7iVb1PNgPqmcknanK5 TdczSnlqWThuKJ+55wQkKRyHpSHt7yGadx+/sh/PLs7xsg8zUNc59YxSHWZIq93Z Dk/sQQR7cXGjbA2Be4IAAQbQGv6nM7+wsWPvRf1y9FKU4JEqlgFDatkHT/kPgcBC XDrA3qlSm3pn4JNoBmrLrKPGs7ksFxhlzB7bZVoA2kMSazo0c7pZFX4g05DxEUmy uqa4KxAc2yLwskCA/Q2TlLyeugTvEGdcswhDr7/AZD9lGpwRbhIfkNaQmMHk1XKb hWBvYIb2OF6sB3izWju9 =zZFf -----END PGP SIGNATURE----- --/+tgMl2zofoPYNwo--