Re: logical decoding : exceeded maxAllocatedDescs for .spill files
| От | Amit Kapila |
|---|---|
| Тема | Re: logical decoding : exceeded maxAllocatedDescs for .spill files |
| Дата | |
| Msg-id | CAA4eK1JitJgbOv-ie3VCXW5A74j-v0b8S55YMunwmkFDZ_4NCg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: logical decoding : exceeded maxAllocatedDescs for .spill files (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: logical decoding : exceeded maxAllocatedDescs for .spill files
Re: logical decoding : exceeded maxAllocatedDescs for .spill files |
| Список | pgsql-hackers |
On Thu, Jan 9, 2020 at 11:15 AM Tom Lane <tgl@sss.pgh.pa.us> wrote: > > Noah Misch <noah@leadboat.com> writes: > > Even so, a web search for "extend_brk" led to the answer. By default, 32-bit > > AIX binaries get only 256M of RAM for stack and sbrk. The new regression test > > used more than that, hence this crash. > > Hm, so > > (1) Why did we get a crash and not some more-decipherable out-of-resources > error? Can we improve that experience? > > (2) Should we be dialing back the resource consumption of this test? > In HEAD, we have a guc variable 'logical_decoding_work_mem' by which we can control the memory usage of changes and we have used that, but for back branches, we don't have such a control. -- With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: