Re: PostgreSQL 12: Feature Highlights
От | Peter Geoghegan |
---|---|
Тема | Re: PostgreSQL 12: Feature Highlights |
Дата | |
Msg-id | CAH2-WznHtAuCcRMrNcocKNy1vN4w4e88d2XCT1fMMFnzjd-KiA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: PostgreSQL 12: Feature Highlights (Michael Paquier <michael@paquier.xyz>) |
Ответы |
Re: PostgreSQL 12: Feature Highlights
|
Список | pgsql-advocacy |
On Thu, May 16, 2019 at 4:52 PM Michael Paquier <michael@paquier.xyz> wrote: > +1. Another thing which may matter is that if some people do not see > some improvements they were expecting then they can come back to pg13 > and help around with having these added. Things are never going to be > perfect for all users, and it makes little sense to make it sound like > things are actually perfect. Speaking of imperfections: it is well known that most performance enhancements have the potential to hurt certain workloads in order to help others. Maybe that was explicitly considered to be a good trade-off when the feature went in, and maybe that was the right decision at the time, but more often it was something that was simply overlooked. There is value in leaving information that helps users discover where a problem may have been introduced -- they can tell us about it, and we can fix it. I myself sometimes look through the release notes in an effort to spot something that might have had undesirable side-effects, especially in areas of the code that I am less knowledgeable about, or have only a vague recollection of. Sometimes that is a reasonable starting point. -- Peter Geoghegan
В списке pgsql-advocacy по дате отправления: