| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thomas Markus <t(dot)markus(at)proventis(dot)net> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: out of memory in backup and restore |
| Date: | 2006-12-15 15:44:34 |
| Message-ID: | 9065.1166197474@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Thomas Markus <t(dot)markus(at)proventis(dot)net> writes:
> logfile content see http://www.rafb.net/paste/results/cvD7uk33.html
It looks to me like you must have individual rows whose COPY
representation requires more than half a gigabyte (maybe much more,
but at least that) and the system cannot allocate enough buffer space.
It could be that this is a symptom of corrupted data, if you're certain
that there shouldn't be any such rows in the table.
> kernel is 2.6.15-1-em64t-p4-smp, pg version is 8.1.0 32bit
You really need a 64-bit PG build if you want to push
multi-hundred-megabyte field values around --- otherwise there's just
not enough headroom in the process address space. (Something newer than
8.1.0 would be a good idea too.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-12-15 15:49:48 | Re: invalid types and tables |
| Previous Message | Joshua Colson | 2006-12-15 15:23:16 | Re: Change "shutdown time" was: Change "database system |