| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Angva" <angvaw(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: out of memory woes |
| Date: | 2006-12-14 16:27:10 |
| Message-ID: | 21351.1166113630@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Angva" <angvaw(at)gmail(dot)com> writes:
> As I've mentioned in a few other posts, I run a daily job that loads
> large amounts of data into a Postgres database. It must run
> efficiently, so one of the tricks I do is run table loads, and commands
> such as cluster, in parallel. I am having a problem where my cluster
> job consistently fails with an out of memory error.
Could we see the actual error message? If it's a server-side error
then there should also be a memory context dump into the postmaster
log, which would be useful to see also. Lastly, please show the full
schema definition (including indexes) for the troublesome tables.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brandon Aiken | 2006-12-14 16:41:57 | Re: out of memory woes |
| Previous Message | Greg Sabino Mullane | 2006-12-14 16:15:41 | Re: Subcribing to this list, what`s the secret? |