From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Wells Oliver <wells(dot)oliver(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-admin <pgsql-admin(at)postgresql(dot)org>, Jeremy Schneider <schnjere(at)amazon(dot)com> |
Subject: | Re: 13.4 on RDS, SSL SYSCALL EOF on restore |
Date: | 2021-10-08 22:48:21 |
Message-ID: | 202110082248.xmzxkwo5gup7@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On 2021-Oct-08, Alvaro Herrera wrote:
> On 2021-Oct-08, Wells Oliver wrote:
>
> > Dug out some more logging:
>
> > 2021-10-08 20:35:08 UTC::@:[12682]:LOG: server process (PID 3970) was terminated by signal 9: Killed
> > 2021-10-08 20:35:08 UTC::@:[12682]:DETAIL: Failed process was running: CREATE INDEX ...
>
> So what's happening here is that the instance is running out of RAM
> while creating some index, and the kernel is killing the process. I
> would probably blame the combination of shared_buffers=4GB with
> maintenance_work_mem=2GB, together with the instance's total RAM.
Also, maybe RDS could be smarter about this situation.
--
Álvaro Herrera Valdivia, Chile — https://www.EnterpriseDB.com/
"La primera ley de las demostraciones en vivo es: no trate de usar el sistema.
Escriba un guión que no toque nada para no causar daños." (Jakob Nielsen)
From | Date | Subject | |
---|---|---|---|
Next Message | Nicolas Ross | 2021-10-08 23:15:55 | Slave stuck in recovery mode |
Previous Message | Alvaro Herrera | 2021-10-08 22:45:59 | Re: 13.4 on RDS, SSL SYSCALL EOF on restore |