Re: BUG #18484: "Cannot enlarge string buffer" during parallel execution of prepared statement/partitioning

Поиск
Список
Период
Сортировка
От Daniel Gustafsson
Тема Re: BUG #18484: "Cannot enlarge string buffer" during parallel execution of prepared statement/partitioning
Дата
Msg-id DFD0B0B3-DF21-4869-AAC9-96744487F767@yesql.se
обсуждение исходный текст
Ответ на Re: BUG #18484: "Cannot enlarge string buffer" during parallel execution of prepared statement/partitioning  (David Rowley <dgrowleyml@gmail.com>)
Ответы Re: BUG #18484: "Cannot enlarge string buffer" during parallel execution of prepared statement/partitioning  (David Rowley <dgrowleyml@gmail.com>)
Список pgsql-bugs
Дерево обсуждения 
> On 30 May 2024, at 03:26, David Rowley <dgrowleyml@gmail.com> wrote:

> I think we should at least write a better error message.  "out of
> memory" is misleading. I've attached a patch with some proposed better
> wording.
>
> The above will become:
> ERROR:  string buffer exceeds maximum allowed length (1073741823)
> DETAIL:  Cannot enlarge string buffer containing 1073741812 bytes by 32 more

Should we use a more human readable unit than bytes in the errmsg as well?

--
Daniel Gustafsson

В списке pgsql-bugs по дате отправления:

Предыдущее
От: David Rowley
Дата:
Сообщение: Re: BUG #18484: "Cannot enlarge string buffer" during parallel execution of prepared statement/partitioning
Следующее
От: Önder Kalacı
Дата:
Сообщение: Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption