Re: ERROR: invalid memory alloc request size 18446744073709551613 - Mailing list pgsql-general

From Flaris Roland Feller
Subject Re: ERROR: invalid memory alloc request size 18446744073709551613
Date
Msg-id B6739903-FA3D-42D5-9DE4-B746650670DC@gmail.com
Whole thread Raw
In response to Re: ERROR: invalid memory alloc request size 18446744073709551613  ("Peter J. Holzer" <hjp-pgsql@hjp.at>)
List pgsql-general
Hello Peter,

In this case, It was a COPY for a table to out of the database, but the error occurs with other commands like a SELECT.

Thanks in advance,
Flaris.

Flaris R. Feller
flaris.feller@gmail.com


Em 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!"

pgsql-general by date:

Previous
From: Flaris Roland Feller
Date:
Subject: Re: ERROR: invalid memory alloc request size 18446744073709551613
Next
From: mohand oubelkacem makhoukhene
Date:
Subject: Implement a new data type