Re: pg_restore out of memory

From: Francisco Reyes <lists(at)stringsutils(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL general <pgsql-general(at)postgresql(dot)org>
Subject: Re: pg_restore out of memory
Date: 2007-06-14 22:10:46
Message-ID: cone.1181859046.421398.38963.5001@35st.simplicato.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tom Lane writes:

> Francisco Reyes <lists(at)stringsutils(dot)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;

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Gregory Stark 2007-06-14 23:12:59 Re: Hash Aggregate plan picked for very large table == out of memory
Previous Message Tom Lane 2007-06-14 21:40:20 Re: Hash Aggregate plan picked for very large table == out of memory