| From: | "Dean Gibson (DB Administrator)" <postgresql(at)mailpen(dot)com> |
|---|---|
| To: | "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: AWS forcing PG upgrade from v9.6 a disaster |
| Date: | 2021-05-28 20:37:41 |
| Message-ID: | 03071c81-aaad-f5ea-7a78-a4acb87960fd@mailpen.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
On 2021-05-28 12:18, Campbell, Lance wrote:
>
> Also, did you check your RDS setting in AWS after upgrading? I run
> four databases in AWS. I found that the work_mem was set way low
> after an upgrade. I had to tweak many of my settings.
>
> Lance
>
>
I've wondered a lot about work_mem. The default setting (which I've
tried) involves a formula, so I have no idea what the actual value is.
Since I have a db.t2.micro (now db.t3.micro) instance with only 1GB of
RAM, I've tried a value of 8000. No difference.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2021-05-28 20:38:10 | Re: AWS forcing PG upgrade from v9.6 a disaster |
| Previous Message | Dean Gibson (DB Administrator) | 2021-05-28 20:33:18 | Re: AWS forcing PG upgrade from v9.6 a disaster |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2021-05-28 20:38:10 | Re: AWS forcing PG upgrade from v9.6 a disaster |
| Previous Message | Dean Gibson (DB Administrator) | 2021-05-28 20:33:18 | Re: AWS forcing PG upgrade from v9.6 a disaster |