Re: pg_restore out of memory - Mailing list pgsql-general

From Francisco Reyes
Subject Re: pg_restore out of memory
Date
Msg-id cone.1181859046.421398.38963.5001@35st.simplicato.com
Whole thread Raw
In response to pg_restore out of memory  (Francisco Reyes <lists@stringsutils.com>)
Responses Re: pg_restore out of memory  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Tom Lane writes:

> Francisco Reyes <lists@stringsutils.com> writes:
>> Syslog was:
>> Jun 14 10:17:56 bk20 postgres[7294]: [130-1] ERROR:  out of memory
>> Jun 14 10:17:56 bk20 postgres[7294]: [130-2] DETAIL:  Failed on request of size 134217728.
>
> Can we see the context-sizes dump that should've come out right before
> that in the log?

Is this the one you need?
Is was right after the error

Jun 14 10:17:56 bk20 postgres[7294]: [130-3] CONTEXT:  COPY message_attachments,
line 60490: "2720290   7225017 research/crew holds.sit sit     88885753        t       1
Jun 14 10:17:56 bk20 postgres[7294]: [130-4]  U3R1ZmZJdCAoYykxOTk3LTIwMDIgQWxhZGRpbiBTeX..."
Jun 14 10:17:56 bk20 postgres[7294]: [130-5] STATEMENT:  COPY
message_attachments (attachment_id, message_id, filename, extension, attachment_size, name_real,
Jun 14 10:17:56 bk20 postgres[7294]: [130-6]  parser_version,
attachment_search_text, attachment_body, delete_status, delete_status_date)
FROM stdin;


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Hash Aggregate plan picked for very large table == out of memory
Next
From: Gregory Stark
Date:
Subject: Re: Hash Aggregate plan picked for very large table == out of memory