Re: Query became very slow after 9.6 -> 10 upgrade
Dmitry Shalashov <skaurus@gmail.com>
From: Dmitry Shalashov <skaurus@gmail.com>
To: Michael Paquier <michael.paquier@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, "pgsql-performance@postgresql.org" <pgsql-performance@postgresql.org>
Date: 2017-11-25T15:39:07Z
Lists: pgsql-hackers, pgsql-performance
> The author is also working on Postgres for 20 years, > so this gives some insurance. I know. Tom is a legend. But still I'd like to hear from him to be sure :) Dmitry Shalashov, relap.io & surfingbird.ru 2017-11-25 15:13 GMT+03:00 Michael Paquier <michael.paquier@gmail.com>: > On Sat, Nov 25, 2017 at 8:54 PM, Dmitry Shalashov <skaurus@gmail.com> > wrote: > > Is it completely safe to use manually patched version in production? > > Patching upstream PostgreSQL to fix a critical bug is something that > can of course be done. And to reach a state where you think something > is safe to use in production first be sure to test it thoroughly on a > stage instance. The author is also working on Postgres for 20 years, > so this gives some insurance. > -- > Michael >
Commits
-
Improve planner's handling of set-returning functions in grouping columns.
- df3a66e282b6 11.0 landed
- b9fc2d0b97c1 10.2 landed