Re: Optimizer items in the release notes - Mailing list pgsql-hackers

From Adrien NAYRAT
Subject Re: Optimizer items in the release notes
Date
Msg-id b0a5e311-5631-e86c-ce8f-09d5a4bd2759@anayrat.info
Whole thread Raw
In response to Optimizer items in the release notes  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On 4/22/19 6:54 PM, Bruce Momjian wrote:
> We had a discussion in October about adding more optimizer items to the
> release notes:
> 
>     https://www.postgresql.org/message-id/flat/20181010220601.GA7807%40momjian.us#11d805ea0b0fcd0552dfa99251417cc1
> 
> There was no agreement on a change, but if people want to propose a
> change, please post here and we can discuss it.
> 

Hello,

Thanks Bruce to start this thread.

I still think it is useful to mention changes in the optimizer for 
several reasons:

- help to understand why a plan can change between different majors 
versions. I don't have any example but an improvement for some users 
could be a regression for others.
- knowing optimizer improvements can motivate users to upgrade to newer 
versions
- help to find bug between majors versions


Regards,



pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: bug in update tuple routing with foreign partitions
Next
From: amul sul
Date:
Subject: Re: [HACKERS] advanced partition matching algorithm forpartition-wise join