| From: | Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com> |
|---|---|
| To: | Michael Harris <michael(dot)harris(at)ericsson(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: ERROR: invalid memory alloc request size when committing transaction |
| Date: | 2021-08-12 09:19:01 |
| Message-ID: | CANbhV-GuYcsSx4y-=r5B2D=TOSvwDbQ1-RV=nUh0q2qFmQpfNw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, 12 Aug 2021 at 06:42, Michael Harris
<michael(dot)harris(at)ericsson(dot)com> wrote:
>
> Thanks Tom,
>
> > How many is "a large number"?
>
> 377k approx.
I'm going to guess that it is the invalidation messages for all the
DDL that is causing the memory allocation error. If you set wal_level
= minimal then this might work.
The total number indicates you are using too many partitions and
should probably lower that by a factor of about 100.
If you do that, you probably won't need to set wal_level.
--
Simon Riggs http://www.EnterpriseDB.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2021-08-12 09:25:52 | Re: 3867653, EMM1 cluster issue on 23rd May--core generated --design feedback |
| Previous Message | Michael Harris | 2021-08-12 05:42:44 | RE: ERROR: invalid memory alloc request size when committing transaction |