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 1hQ8YB-0002AJ-QD for pgsql-advocacy@arkaria.postgresql.org; Mon, 13 May 2019 10:51:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hQ8Y9-0002Xo-GR for pgsql-advocacy@arkaria.postgresql.org; Mon, 13 May 2019 10:51:17 +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 1hQ8Y9-0002Xh-5Z for pgsql-advocacy@lists.postgresql.org; Mon, 13 May 2019 10:51:17 +0000 Received: from mail-io1-xd42.google.com ([2607:f8b0:4864:20::d42]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hQ8Y4-0008Lo-Kt for pgsql-advocacy@lists.postgresql.org; Mon, 13 May 2019 10:51:16 +0000 Received: by mail-io1-xd42.google.com with SMTP id e19so9632252iob.3 for ; Mon, 13 May 2019 03:51:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=1wfhMS1c8HIiDRdBxuCiitDjgNK+od7D2Tv2GzdKRmY=; b=h0k955IPjKxCDNO0/JoePsXGWFpM+DoPSWE0CUyOU0a4YDCFd0wC4d4Y2phrkKo4+D 8zqdm5G9Wtyb9mbwGFO3ow64wNi8I58WgLDjrkr8Zgpvj+bUgnrrJSv8BE2HHBsM9b2Y Z/4B6YtDPthqYgK4zSA5NECMI1rfy8MRm3npvERL00N2OJGJVJhbbHAoVuoQlUJkRsbs WKKR3qAGQ7tyLtsprTP+02R8HtQLAzQ0A+ndCrPmqn8Up8hYFAAYHG5bA6sOCsXu+csG +/Ww/co3DW+pCNnmSVr3sFFAnEiJhX6gUOjkJxQgIAxsTbTz545jNMN7YtgtEbSUEpjU XPNg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=1wfhMS1c8HIiDRdBxuCiitDjgNK+od7D2Tv2GzdKRmY=; b=HO/S6cOm1ZuvsXyybcPHmFq9gN4X6gnB5Tz/2/96iWJ/BLmfMapYHbLqYGxhqGsSCi FcRHsQD68yw6zNFkhBoTTEU+zeVxtq6Q2BPPkkD8cr7Xw679Ice5aSynkPrFX2I1nOB0 W/5KTJhpFBpjtr2rM3grctTYHIcNG3KJDRDPt+hB8a1td8NBUasX7gFnTFbDmXF6J7vr 9oxCT7/HLzJIA0OIAFW6kYGcBMpDQ7dcJ/Msy0Ah5wk2PMh2oU+th9hWeXY4vZqwP4SF EczgcrTPLqMcB5LINOmrltimINpT4OSJS6dep7bMznUQosgU3dSnxKzkpC5nRaYF1BHX GhLQ== X-Gm-Message-State: APjAAAVeo5MVaensvkuopJfq0patN3wx+36A9+yyirwBdXuwYQmEVno2 kghHGsPJ1MwBbCJBUboCd3LORNdwHmT+/eM1/khL/Q== X-Google-Smtp-Source: APXvYqywMMZ3vA5C1DjnQmYdtmkbAVZFXC0OSBuGHpLjx/pjf4nvLr65ngd6yCqsa0LTz2CRcvUgDy7Adjask5wG4VE= X-Received: by 2002:a5d:9153:: with SMTP id y19mr12672384ioq.38.1557744670786; Mon, 13 May 2019 03:51:10 -0700 (PDT) MIME-Version: 1.0 References: <830415f7-78ec-ef7b-0f73-0e810ef87f91@postgresql.org> <3ea29ec1-38e9-b5bd-571e-8d1f85175c5a@lab.ntt.co.jp> In-Reply-To: <3ea29ec1-38e9-b5bd-571e-8d1f85175c5a@lab.ntt.co.jp> From: David Rowley Date: Mon, 13 May 2019 22:50:59 +1200 Message-ID: Subject: Re: PostgreSQL 12: Feature Highlights To: Amit Langote Cc: Justin Clift , "Jonathan S. Katz" , pgsql-advocacy@lists.postgresql.org Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Mon, 13 May 2019 at 18:37, Amit Langote wrote: > It's true that optimizer and executor can now handle larger number of > partitions efficiently, but the improvements in this release will only be > meaningful to workloads where partition pruning is crucial, so I don't see > why mentioning "pruning" is so misleading. Perhaps, it would be slightly > misleading to not mention it, because readers might think that queries > like this one: > > select count(*) from partitioned_table; > > are now faster in v12, whereas AFAIK, they perform perform more or less > the same as in v11. This is true, but whether partitions are pruned or not is only relevant to one of the many items the headline feature is talking about. I'm not sure how you'd briefly enough mention that fact without going into detail about which features are which and which are affected by partition pruning. I think these are the sorts of details that can be mentioned away from the headline features, which is why I think lumping these all in one in the main release notes is a bad idea as it's pretty hard to do that when they're all lumped in as one item. -- David Rowley http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services