From: | Japin Li <japinli(at)hotmail(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Invalid memory alloc request size for repeat() |
Date: | 2022-05-26 01:02:08 |
Message-ID: | MEYP282MB166974FCD609CCCDB366766FB6D99@MEYP282MB1669.AUSP282.PROD.OUTLOOK.COM |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 25 May 2022 at 22:41, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Wednesday, May 25, 2022, Japin Li <japinli(at)hotmail(dot)com> wrote:
>
>>
>> Hi,
>>
>> Today, I try to use repeat() to generate 1GB text, and it occurs invalid
>> memory
>> alloc request size [1]. It is a limit from palloc(), then I try to reduce
>> it,
>> it still complains out of memory which comes from enlargeStringInfo()
>> [2]. The
>> documentation about repect() [3] doesn't mentaion the limitation.
>>
>
> That is still a “field” even if it is not stored.
>
> https://www.postgresql.org/docs/current/limits.html
>
I mean this is a limitation about repect() function, it isn't really about 1GB,
we can only use 1GB - 4 for it.
--
Regrads,
Japin Li.
ChengDu WenWu Information Technology Co.,Ltd.
From | Date | Subject | |
---|---|---|---|
Next Message | Japin Li | 2022-05-26 01:03:54 | Re: Invalid memory alloc request size for repeat() |
Previous Message | Michael Paquier | 2022-05-26 00:51:04 | Re: adding status for COPY progress report |