| From: | Michael Lewis <mlewis(at)entrata(dot)com> |
|---|---|
| To: | Ryan Bair <ryandbair(at)gmail(dot)com> |
| Cc: | "Dean Gibson (DB Administrator)" <postgresql(at)mailpen(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Pgsql Performance <pgsql-performance(at)lists(dot)postgresql(dot)org>, lance(at)illinois(dot)edu |
| Subject: | Re: AWS forcing PG upgrade from v9.6 a disaster |
| Date: | 2021-05-28 20:11:09 |
| Message-ID: | CAHOFxGpjKvU4=JVxeVf=x9U+8iO-R9DHOMSwfHq+GMnXfpD1Xg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
The plan is also influenced by cost related and memory related config
settings such as random_page_cost and work_mem, right? Hence the questions
if configs are matching or newer versions are using very conservative
(default) settings.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 2021-05-28 20:23:06 | Re: AWS forcing PG upgrade from v9.6 a disaster |
| Previous Message | Ryan Bair | 2021-05-28 19:39:23 | Re: AWS forcing PG upgrade from v9.6 a disaster |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 2021-05-28 20:23:06 | Re: AWS forcing PG upgrade from v9.6 a disaster |
| Previous Message | Ryan Bair | 2021-05-28 19:39:23 | Re: AWS forcing PG upgrade from v9.6 a disaster |