Re: Postgres server 12.2 crash with process exited abnormally and possibly corrupted shared memory

On Tue, Jun 9, 2020 at 8:35 AM Ishan Joshi <Ishan(dot)Joshi(at)amdocs(dot)com> wrote:

> I have using postgresql server v12.2 on CentOS Linux release 7.3.1611
> (Core).
>
>
>
> My application is working fine with non partition tables but recently we
> are trying to adopt partition table on few of application tables.
>
> So we have created List partition on 6 table. 2 out of 6 tables have 24
> partitions and 4 out of 6 tables have 500 list partitions. After performing
> partition table, we are trying to run our application it is getting crash
> as I can see the memory utilization is consumed 100% and once it reach to
> 100% Postgres server getting crash with following error
>

How many rows did these tables have before partitioning? Why did you decide
to partition? Do these list partitions allow for plan-time pruning? Do they
support partition wise joins? work_mem can be used for each node of the
plan and if you are getting parallel scans of many tables or indexes where
you previously had one, that could be an issue.

2000 for max_connections strikes me as quite high. Consider the use of a
connection pooler like pgbouncer or pgpool such that Postgres can be run
with max connections more like 2-5x your number of CPUs, and those
connections get re-used as needed. There is some fixed memory overhead for
each potential connection.