From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Adam Brusselback <adambrusselback(at)gmail(dot)com> |
Cc: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Optimizer items in the release notes |
Date: | 2019-04-26 23:49:14 |
Message-ID: | 20190426234914.2ymb33tdwpnj2wdm@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Apr 24, 2019 at 02:46:15PM -0400, Adam Brusselback wrote:
> As a user, I am interested in the optimizer changes for sure, and I
> actually had wished they were highlighted more in previous releases.
>
> > I think planner smarts are arguably one of our weakest areas when
> > compared to the big commercial databases. The more we can throw in
> > there about this sort of thing the better.
>
> Completely agree on both fronts. I have run into numerous
> optimizations I had taken for granted when I worked primarily with SQL
> Server and were not present in Postgres. Work being done to make the
> Postgres optimizer smarter is great, as is highlighting that work in
> the release notes IMO.
This thread highlights the challenges of having optimizer items in the
release notes:
* They often reply to only a small percentage of queries
* They are hard to explain
I see the argument as wanting vague warm and fuzzy feelings that we are
improving the optimizer, which we are. I will see what I can do to get
those ideas into the PG 12 release notes in as concrete a way as
possible.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2019-04-26 23:53:13 | Re: What is an item pointer, anyway? |
Previous Message | Ashwin Agrawal | 2019-04-26 23:23:44 | Re: What is an item pointer, anyway? |