> On Mar 13, 2023, at 12:25 PM, Joe Conway <mail@xxxxxxxxxxxxx> wrote: > > On 3/13/23 16:18, Israel Brewster wrote: >>> Did you try setting "vm.overcommit_memory=2"? > >> root@novarupta:~# sysctl -w vm.overcommit_memory=2 >> sysctl: setting key "vm.overcommit_memory", ignoring: Read-only file system > >> I’m thinking I wound up with a container rather than a full VM after >> all - and as such, the best solution may be to migrate to a full VM >> with some swap space available to avoid the issue in the first place. >> I’ll have to get in touch with the sys admin for that though. > > Hmm, well big +1 for having swap turned on, but I recommend setting "vm.overcommit_memory=2" even so. Makes sense. Presumably with a full VM I won’t get the “Read-only file system” error when trying to do so. Thanks! --- Israel Brewster Software Engineer Alaska Volcano Observatory Geophysical Institute - UAF 2156 Koyukuk Drive Fairbanks AK 99775-7320 Work: 907-474-5172 cell: 907-328-9145 > > -- > Joe Conway > PostgreSQL Contributors Team > RDS Open Source Databases > Amazon Web Services: https://aws.amazon.com >
