| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Dmitry Shalashov <skaurus(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Query became very slow after 9.6 -> 10 upgrade |
| Date: | 2017-11-25 12:13:42 |
| Message-ID: | CAB7nPqQkVkEmQ29bWE8i_D7Sg1zEx9YptEuKR7_N0o7p_K7BNQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
On Sat, Nov 25, 2017 at 8:54 PM, Dmitry Shalashov <skaurus(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-11-25 14:04:14 | Re: Treating work_mem as a shared resource (Was: Parallel Hash take II) |
| Previous Message | Dmitry Shalashov | 2017-11-25 11:54:55 | Re: Query became very slow after 9.6 -> 10 upgrade |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dmitry Shalashov | 2017-11-25 15:39:07 | Re: Query became very slow after 9.6 -> 10 upgrade |
| Previous Message | Dmitry Shalashov | 2017-11-25 11:54:55 | Re: Query became very slow after 9.6 -> 10 upgrade |