From: Dean Gibson (DB Administrator) <postgresql@mailpen.com>
To: pgsql-performance@lists.postgresql.org <pgsql-performance@lists.postgresql.org>
Subject: Re: AWS forcing PG upgrade from v9.6 a disaster
Date: Fri, 28 May 2021 13:37:41 -0700
Message-ID: <03071c81-aaad-f5ea-7a78-a4acb87960fd@mailpen.com> (raw)
In-Reply-To: <SN6PR11MB3326479A2100FF2A578CD1FCDE229@SN6PR11MB3326.namprd11.prod.outlook.com>
References: <88dec70b-eb63-0b72-0b5d-253851ef127b@mailpen.com>
<9fa75894-d3be-e40b-cd89-f641bdf85df0@dunslane.net>
<SN6PR11MB3326479A2100FF2A578CD1FCDE229@SN6PR11MB3326.namprd11.prod.outlook.com>
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: postgresql@mailpen.com, pgsql-performance@lists.postgresql.org
Subject: Re: AWS forcing PG upgrade from v9.6 a disaster
In-Reply-To: <03071c81-aaad-f5ea-7a78-a4acb87960fd@mailpen.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox