Re: ERROR: invalid memory alloc request size 18446744073709551613

Поиск
Список
Период
Сортировка
От Flaris Feller
Тема Re: ERROR: invalid memory alloc request size 18446744073709551613
Дата
Msg-id CANNsrHs2ikr+DjW_EUVTxgeaMq+fnqove1fKTp9a9LtJ35aQJA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: ERROR: invalid memory alloc request size 18446744073709551613  ("Peter J. Holzer" <hjp-pgsql@hjp.at>)
Ответы Re: ERROR: invalid memory alloc request size 18446744073709551613  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-general
Hi Peter,

The error happens with SELECT command too and the COPY command was used to extract data out of the database.

Thanks in advance,
Flaris Feller.

Em seg., 22 de jun. de 2020 às 12:33, Peter J. Holzer <hjp-pgsql@hjp.at> escreveu:
On 2020-06-22 11:13:33 -0300, Flaris Feller wrote:
> When using Postgres 9.6.15 on "CentOS Linux release 7.5.1804 (Core)" on Intel
> x86_64 I noticed "invalid memory alloc request size" error at PostgreSQL logs.
> This is the postgresq.log file's fragment of log where the error was found.
>
> 2020-06-22 00:29:18 BRT [16987]: [1-1] db=bxs,user=postgres ERRO:  invalid
> memory alloc request size 18446744073709551613

That's 2**64 - 3. So probably the size of some object is (erroneously)
computed as -3 bytes.

> 2020-06-22 00:29:18 BRT [16987]: [2-1] db=bxs,user=postgres COMANDO:  COPY
> public.cham_chamada....

Does this always happen in conjunction with a COPY command or sometimes
with other commands, too? If the former, are you copying into the
database or out of it?

        hp

--
   _  | Peter J. Holzer    | Story must make more sense than reality.
|_|_) |                    |
| |   | hjp@hjp.at         |    -- Charles Stross, "Creative writing
__/   | http://www.hjp.at/ |       challenge!"


--
Flaris Roland Feller
48-999811781

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

Предыдущее
От: Michel Pelletier
Дата:
Сообщение: Re: Hiding a GUC from SQL
Следующее
От: Michael Lewis
Дата:
Сообщение: Re: DISTINCT on jsonb fields and Indexes