Tom Lane writes:
Francisco Reyes <[EMAIL PROTECTED]> 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;
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
