Re: invalid memory alloc request size

From: Gabriel Sánchez Martínez <gabrielesanchez(at)gmail(dot)com>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: invalid memory alloc request size
Date: 2014-12-10 17:25:16
Message-ID: 548881FC.6070302@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


On 12/10/2014 11:49 AM, Adrian Klaver wrote:
> On 12/10/2014 08:31 AM, Gabriel Sánchez Martínez wrote:
>>
>> On 12/10/2014 11:16 AM, Adrian Klaver wrote:
>>> On 12/10/2014 08:07 AM, Gabriel Sánchez Martínez wrote:
>>>> Hi all,
>>>>
>>>> I am running PostgreSQL 9.3.5 on Ubuntu Server 14.04 64 bit with 64 GB
>>>> of RAM. When running pg_dump on a specific table, I get the following
>>>> error:
>>>>
>>>> pg_dump: Dumping the contents of table "x_20131111" failed:
>>>> PQgetResult() failed.
>>>> pg_dump: Error message from server: ERROR: invalid memory alloc
>>>> request
>>>> size 18446744073709551613
>>>> pg_dump: The command was: COPY public.x_20131111 (...) TO stdout;
>>>> pg_dump: [parallel archiver] a worker process died unexpectedly
>>>>
>>>> If I run a COPY TO file from psql I get the same error.
>>>>
>>>> Is this an indication of corrupted data? What steps should I take?
>>>
>>>
>>> What is the data that is being dumped, for example is there binary
>>> data in there?
>>
>> The data types are bigserial, integer, and character varying.
>>
>>>
>>> What is the table definition?
>>
>> The data is confidential so I have obfuscated the names:
>>
>> CREATE TABLE x
>> (
>> c01 bigserial NOT NULL,
>> c02 integer NOT NULL,
>> c03 integer NOT NULL,
>> c04 integer NOT NULL,
>> c05 integer,
>> c06 integer,
>> c07 integer,
>> c08 integer,
>> c09 integer,
>> c10 integer,
>> c11 integer,
>> c12 integer,
>> c13 character varying(8),
>> c14 integer,
>> c15 integer,
>> c16 character varying(8),
>> c17 integer,
>> c18 character varying(8),
>> c19 integer,
>> c20 integer,
>> c21 integer,
>> c22 integer,
>> c23 integer,
>> c24 integer,
>> c25 integer,
>> c26 integer,
>> c27 integer,
>> c28 integer,
>> c29 integer,
>> c30 integer,
>> c31 integer,
>> c32 integer,
>> c33 integer,
>> CONSTRAINT "PK_x" PRIMARY KEY (c01)
>> )
>>
>>>
>>> Would it be possible to show the header and some sample data from the
>>> COPY?
>>
>> Here is the first row using SELECT * LIMIT 1:
>>
>> 776696816;12368;47728024;3959;0;256;765;645;309;336;36;102;"";;;"";;"";;-1;0;0;0;0;-1;-1;0;0;5;28;;0;37
>>
>
> How did the database get to this machine?
>
> Was it created from scratch or did it come from somewhere else?

The database was created from a pg_dump backup using pg_restore. The
table has not changed since the backup date, so I could try re-creating
it the same way, but that doesn't solve the mystery.

>
> Also how did the Postgres server get installed?

apt-get install

>
>
>>
>>
>>>
>>>>
>>>> Thanks in advance,
>>>> Gabriel
>>>>
>>>>
>>>
>>>
>>
>
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2014-12-10 17:47:14 Re: invalid memory alloc request size
Previous Message Alex Shulgin 2014-12-10 16:53:32 Re: Current log files when rotating?